Re: [Qemu-devel] [PATCH 2/8] libqos: Handle PCI IO de-multiplexing in common code

2016-10-18 Thread David Gibson
On Tue, Oct 18, 2016 at 03:28:17PM +0200, Laurent Vivier wrote: > > > On 18/10/2016 12:52, David Gibson wrote: > > The PCI IO space (aka PIO, aka legacy IO) and PCI memory space (aka MMIO) > > are distinct address spaces by the PCI spec (although parts of one might be > > aliased to parts of the

Re: [Qemu-devel] [PATCH 2/8] libqos: Handle PCI IO de-multiplexing in common code

2016-10-18 Thread Laurent Vivier
On 18/10/2016 12:52, David Gibson wrote: > The PCI IO space (aka PIO, aka legacy IO) and PCI memory space (aka MMIO) > are distinct address spaces by the PCI spec (although parts of one might be > aliased to parts of the other in some cases). > > However, qpci_io_read*() and qpci_io_write*() can

[Qemu-devel] [PATCH 2/8] libqos: Handle PCI IO de-multiplexing in common code

2016-10-18 Thread David Gibson
The PCI IO space (aka PIO, aka legacy IO) and PCI memory space (aka MMIO) are distinct address spaces by the PCI spec (although parts of one might be aliased to parts of the other in some cases). However, qpci_io_read*() and qpci_io_write*() can perform accesses to either space depending on parame