Re: [Xen-devel] xhci_hcd intterrupt affinity in Dom0/DomU limited to single interrupt

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 16.09.15 at 22:31, <ackerj68@xxxxxxxxx> wrote:
> I think the lspci -v output is the same in both cases with the exception
> of the xhci_pci which is not present in the Native case lspci -v output.
> xhci_pci is built into the kernel. The same kernel/system is used with
> this system when booted with Dom0 and native cases. I could rebuild the
> kernel without it and see what happens? 

No point in doing so, the only lines we're interesting in here are ...

> Native:
> 
> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
> Family USB xHCI (rev 05) (prog-if 30 [XHCI])
>       Subsystem: Intel Corporation 8 Series/C220 Series Chipset Family USB
> xHCI
>       Flags: bus master, medium devsel, latency 0, IRQ 27
>       Memory at f7e20000 (64-bit, non-prefetchable) [size=64K]
>       Capabilities: [70] Power Management version 2
>       Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+

... this and ...

>       Kernel driver in use: xhci_hcd
> 
> 
> 
> Dom0:
> 
> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
> Family USB xHCI (rev 05) (prog-if 30 [XHCI])
>       Subsystem: Intel Corporation 8 Series/C220 Series Chipset Family USB
> xHCI
>       Flags: bus master, medium devsel, latency 0, IRQ 76
>       Memory at f7e20000 (64-bit, non-prefetchable) [size=64K]
>       Capabilities: [70] Power Management version 2
>       Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+

... this. Them being identical proves what I suspected: The driver
uses only a single interrupt.

Jan


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