Re: [Xen-devel] Failure: passthrough of 2 PCIe devices - regression of "QEMU passthrough: support PV on HVM MSI remapping"

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

> (XEN) [VT-D]io.c:327: d3: unbind: m_gsi=0 g_gsi=36 device=5 intx=0
> (XEN) [VT-D]io.c:386: d3 unmap: m_irq=0 device=5 intx=0
> (XEN) [VT-D]io.c:303: d3: bind: m_gsi=17 g_gsi=36 device=5 intx=0
> (XEN) domctl.c:920:d0 pt_irq_create_bind failed!
> (XEN) irq.c:1590: dom3: forcing unbind of pirq 0
> 
> In xen-4.0 (SLES11-SP1) all went fine.
> I saw some added code in tools/ioemu-remote/hw/pt-msi.c function 
> pt_msi_setup()
> in xen-unstable:

Hmmm, that is Stefano's code (git log -p hw/pt-msi.c)

Lets ask him.
> 
>     gvec = dev->msi->data & 0xFF;
>     if (!gvec) {
>         /* if gvec is 0, the guest is asking for a particular pirq that
>          * is passed as dest_id */
>         pirq = (dev->msi->addr_hi & 0xffffff00) |
>                ((dev->msi->addr_lo >> MSI_TARGET_CPU_SHIFT) & 0xff);
>         PT_LOG("pt_msi_setup requested pirq = %d\n", pirq);
>     }
> 
> If I remove this code the device 00:1b.0 gets pirq 37 and 00:10.0 gets pirq 
> 36.
> Now at least device 00:10.0 (WLAN) works. The audio device is still another 
> problem.
> 
> Is this a already seen problem after all these msi discussions on the list?
> Thanks!
> 
> Dietmar.
> 
> 
> -- 
> Company details: http://ts.fujitsu.com/imprint.html

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel