Re: [Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Benjamin Herrenschmidt
On Fri, 2013-06-21 at 06:58 -0500, Anthony Liguori wrote: > > I do not understand the question, really. Here we are emulating pHyp which > > is not real hardware and never pretended to be. Our guests do not touch MSI > > records in the config space and use RTAS MSI calls instead. > > But RTAS is i

Re: [Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Benjamin Herrenschmidt
On Fri, 2013-06-21 at 12:31 +0200, Alexander Graf wrote: > On 21.06.2013, at 11:22, Alexey Kardashevskiy wrote: > > > Previously every PCI host bridge implemented its own MSI memory window > > in order to catch msi_notify()/msix_notify() calls from various QEMU > > MSI-capable devives such as virt

Re: [Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Alexander Graf
On 21.06.2013, at 13:58, Anthony Liguori wrote: > Alexey Kardashevskiy writes: > >> On 06/21/2013 08:31 PM, Alexander Graf wrote: >>> >>> On 21.06.2013, at 11:22, Alexey Kardashevskiy wrote: >>> Previously every PCI host bridge implemented its own MSI memory window in order to catch

Re: [Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Anthony Liguori
Alexey Kardashevskiy writes: > On 06/21/2013 08:31 PM, Alexander Graf wrote: >> >> On 21.06.2013, at 11:22, Alexey Kardashevskiy wrote: >> >>> Previously every PCI host bridge implemented its own MSI memory window >>> in order to catch msi_notify()/msix_notify() calls from various QEMU >>> MSI-

Re: [Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Alexey Kardashevskiy
On 06/21/2013 08:31 PM, Alexander Graf wrote: > > On 21.06.2013, at 11:22, Alexey Kardashevskiy wrote: > >> Previously every PCI host bridge implemented its own MSI memory window >> in order to catch msi_notify()/msix_notify() calls from various QEMU >> MSI-capable devives such as virtio-pci or v

Re: [Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Alexander Graf
On 21.06.2013, at 11:22, Alexey Kardashevskiy wrote: > Previously every PCI host bridge implemented its own MSI memory window > in order to catch msi_notify()/msix_notify() calls from various QEMU > MSI-capable devives such as virtio-pci or vfio and redirect them to > the guest via qemu_pulse_irq

[Qemu-devel] [PATCH 1/3] spapr pci msi: rework

2013-06-21 Thread Alexey Kardashevskiy
Previously every PCI host bridge implemented its own MSI memory window in order to catch msi_notify()/msix_notify() calls from various QEMU MSI-capable devives such as virtio-pci or vfio and redirect them to the guest via qemu_pulse_irq(). The encoded MSIMessage used to be encoded as: * .addr - ad