Re: [Xen-devel] [Xen-unstable] regression in pci passthrough to HVM guests due to commit 568da4f8c43d2e5b614964c6aefd768de3e3af14 "pt-irq fixes and improvements".

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Tuesday, August 5, 2014, 10:30:26 AM, you wrote:

>>>> On 04.08.14 at 14:29, <linux@xxxxxxxxxxxxxx> wrote:
>> I'm experiencing a regression in pci passthrough to HVM guests due to commit 
>> 
>> 568da4f8c43d2e5b614964c6aefd768de3e3af14 "pt-irq fixes and improvements".
>> 
>> Before it used to be fine to shutdown and restart guests with the same pci 
>> devices passed through. After this commit it doesn't, the device is passed 
>> through and visible but doesn't function properly (for instance when passing 
>> 
>> through a USB card, a "lsusb" fails.
>> 
>> From the logs i see there is (at least) a problem with unmapping the irqs at 
>> the 
>> shutdown of the guest, after this commit it gives:
>> 
>> (XEN) [2014-08-04 11:15:48.783] irq.c:2119: dom1: forcing unbind of pirq 87
>> (XEN) [2014-08-04 11:15:48.783] irq.c:2119: dom1: forcing unbind of pirq 86
>> (XEN) [2014-08-04 11:15:48.783] irq.c:2119: dom1: forcing unbind of pirq 85
>> (XEN) [2014-08-04 11:15:48.783] irq.c:2119: dom1: forcing unbind of pirq 84

> And I can see what went wrong: The shortcut to do nothing for
> PT_IRQ_TYPE_MSI was wrong, albeit I'm confused that you saw
> this (also) with pci_msitranslate=1 - the hypervisor log you sent
> suggests it's being ignored (or at least doesn't lead to
> PT_IRQ_TYPE_MSI_TRANSLATE being used), or else there should
> have been at least a "d1: unbind: ..." message.

Could be that i captured the logs while trying out the "pci_msitranslate=0" (to 
see if it made any difference).

> I'm testing a fix...

> Jan




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel