similar to: [PATCH v2 0/2] MSI/MSIX injection for Xen HVM guests

Implement a simple Xen APIC module and use it to deliver MSI/MSIX for Xen HVM guests.

Hi all, this small patch series fixes the build breakage introduced by f1dbf015dfb0aa7f66f710a1f1bc58b662951de2 with Xen < 4.2. The problem is that xc_hvm_inject_msi is only defined from Xen 4.2 onwards so we need to provide a compatibility function for older Xen versions. Stefano Stabellini (2): xen,configure: detect Xen 4.2 xen: add a dummy xc_hvm_inject_msi for Xen < 4.2

Support PV on HVM MSIX remapping The technique is the same used with MSI: if the guest enables an MSIX passing 0 as vector number, then read the address and use it as pirq number for the following mapping request to Xen. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff --git a/hw/pt-msi.c b/hw/pt-msi.c index f0fb3e3..b01744e 100644 --- a/hw/pt-msi.c +++

Don't add an option for platforms to disable MSI-X in all devices. Paul Brook will find and fix all platforms that have broken MSI-X emulation. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- This patch on top of my msix series v6 is a bit tongue in cheek: it shows what can be done and Paul seems to think it's a good idea. So even though I don't necessarily agree,

Don't add an option for platforms to disable MSI-X in all devices. Paul Brook will find and fix all platforms that have broken MSI-X emulation. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- This patch on top of my msix series v6 is a bit tongue in cheek: it shows what can be done and Paul seems to think it's a good idea. So even though I don't necessarily agree,

On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net

On Sun, Jan 04, 2015 at 04:38:17PM +0800, Jason Wang wrote: > > On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote: > > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > >> Hi all: > >> > >> This series try to share MSIX irq for each tx/rx queue pair. This is > >> done through: > >> > >> - introducing virtio pci channel

Jason Wang <jasowang at redhat.com> writes: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net (Patch 3)

On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net

On Sun, Jan 04, 2015 at 04:38:17PM +0800, Jason Wang wrote: > > On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote: > > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > >> Hi all: > >> > >> This series try to share MSIX irq for each tx/rx queue pair. This is > >> done through: > >> > >> - introducing virtio pci channel

Jason Wang <jasowang at redhat.com> writes: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net (Patch 3)

This patch try to reduce the number of MSIX irqs required for virtio-net by sharing a MSIX irq for each TX/RX queue pair through channels. If transport support channel, about half of the MSIX irqs were reduced. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael S. Tsirkin <mst at redhat.com> Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/net/virtio_net.c |

This patch try to reduce the number of MSIX irqs required for virtio-net by sharing a MSIX irq for each TX/RX queue pair through channels. If transport support channel, about half of the MSIX irqs were reduced. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael S. Tsirkin <mst at redhat.com> Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/net/virtio_net.c |

On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote: > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: >> Hi all: >> >> This series try to share MSIX irq for each tx/rx queue pair. This is >> done through: >> >> - introducing virtio pci channel which are group of virtqueues that >> sharing a single MSIX irq (Patch 1) >> - expose channel

On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote: > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: >> Hi all: >> >> This series try to share MSIX irq for each tx/rx queue pair. This is >> done through: >> >> - introducing virtio pci channel which are group of virtqueues that >> sharing a single MSIX irq (Patch 1) >> - expose channel

On (Tue) Jul 21 2009 [19:54:00], Michael S. Tsirkin wrote: > On Fri, Jul 17, 2009 at 06:34:40PM +0530, Amit Shah wrote: > > Hello, > > > > Using recent qemu-kvm userspace with a slightly older kernel module I > > get this when using the virtio-net device: I was getting this with a very recent kernel in the guest with an older host kernel. 2.6.31-rc3 in the guest and

On (Tue) Jul 21 2009 [19:54:00], Michael S. Tsirkin wrote: > On Fri, Jul 17, 2009 at 06:34:40PM +0530, Amit Shah wrote: > > Hello, > > > > Using recent qemu-kvm userspace with a slightly older kernel module I > > get this when using the virtio-net device: I was getting this with a very recent kernel in the guest with an older host kernel. 2.6.31-rc3 in the guest and

Hi maintainer, Reprodue an bug on xen-unstable, it''s an irq affinity issue for passthroughed msix device to uek1 pvhvm(2.6.32 stable). I passthrough two mptsas devices(0000:0d:0.0, 0000:1f:0.0) to a pvhvm, irq affinity can''t be changed. Step to reproduce is as below: 1. xl -f pci-assignable-add 0000:0d:0.0; xl -f pci-assignable-add 0000:1f:0.0 2.xm cr -c vm.cfg

For assigned devices, use common code to enable msi-x. We need a special "assigned" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 329 ++++++++++++------------------------------------ hw/device-assignment.h | 7 +- hw/msix.c | 9 ++- hw/pci.h

For assigned devices, use common code to enable msi-x. We need a special "assigned" option as assigned devices lack a standard way to get vector usage. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/device-assignment.c | 329 ++++++++++++------------------------------------ hw/device-assignment.h | 7 +- hw/msix.c | 9 ++- hw/pci.h