Re: [Xen-devel] Xen-unstable: pci-passthrough "irq 16: nobody cared" on HVM guest shutdown on irq of device not passed through.

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 01.10.14 at 15:52, <linux@xxxxxxxxxxxxxx> wrote:
> Just tested with about the same kernel (and same hardware) on linux + kvm:
> 
> When i boot i see (on the host):
> [    1.341556] pcieport 0000:00:02.0: irq 31 for MSI/MSI-X
> [    1.341875] pcieport 0000:00:03.0: irq 32 for MSI/MSI-X
> [    1.342145] pcieport 0000:00:05.0: irq 33 for MSI/MSI-X
> [    1.342429] pcieport 0000:00:06.0: irq 34 for MSI/MSI-X
> [    1.342588] pcieport 0000:00:09.0: irq 35 for MSI/MSI-X
> [    1.342853] pcieport 0000:00:0a.0: irq 36 for MSI/MSI-X
> [    1.343125] pcieport 0000:00:0b.0: irq 37 for MSI/MSI-X
> [    1.343285] pcieport 0000:00:0c.0: irq 38 for MSI/MSI-X
> [    1.343434] pcieport 0000:00:0d.0: irq 39 for MSI/MSI-X
> [    1.343719] pcieport 0000:00:15.0: irq 40 for MSI/MSI-X
> [    1.343897] pcieport 0000:05:00.0: irq 41 for MSI/MSI-X
> [    1.344134] pcieport 0000:06:01.0: irq 42 for MSI/MSI-X
> [    1.344398] pcieport 0000:06:02.0: irq 44 for MSI/MSI-X
> 
> While the soundcard has still irq16.

Where MSIs get allocated has nothing to do with pin based IRQs. Or
maybe I'm just not understanding what you're trying to tell me...

> Passing through 09:00.0 to a KVM guest (as primary passthrough since that 
> works 
> with KVM) it works fine and after shutting down there is no "irq 16 nobody 
> cared".
> 
> So why would linux setup those irq/gsi's for the pcieport differently on Xen 
> and on 
> baremetal (and why can a irq/gsi be bound to 2 devices) ? 

Without seeing both logs at the same time I can't even tell what
the difference is. Rather than keeping all kinds of irrelevant (for
the moment) context it would have helped more if you had added
the respective Xen side messages.

That said - questions about upstream Linux interrupt setup
would better be directed to the upstream Xen Linux maintainers.

Jan


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