[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] xhci_hcd intterrupt affinity in Dom0/DomU limited to single interrupt
On Fri, 2015-09-11 at 04:03 -0600, Jan Beulich wrote: >>> On 10.09.15 at 18:20, <ackerj67@xxxxxxxxx> wrote: > On Wed, 2015-09-09 at 00:48 -0600, Jan Beulich wrote: >> >>> On 08.09.15 at 18:02, <ackerj67@xxxxxxxxx> wrote: >> > I believe the driver does support use of multiple interrupts based on >> > the previous explanation of the lspci output where it was established >> > that the device could use up to 8 interrupts which is what I see on bare >> > metal. >> >> Where is the proof of that? All I've seen is output like this >> >> Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ >> >> which says that one out of eight interrupts is being used. And >> if in the native case this would indeed be the case, I don't think >> you've provided complete hypervisor and kernel logs for the >> Xen case so far, which would allow us to look for respective error >> indications. And this (ignoring the line wrapping, which makes >> things hard to read - it would be appreciated if you could fix >> your mail client)... >> >> > Bare metal: >> > >> > cat /proc/interrupts >> > CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 >> > CPU6 CPU7 >> > 0: 36 0 0 0 0 0 >> > 0 0 IR-IO-APIC-edge timer >> >[...] >> > 27: 337125 47893 708965 4049 53940667 263303 >> > 87847 4958 IR-PCI-MSI-edge xhci_hcd >> >> ... also shows just a single interrupt being in use. > > Kernel logs for native and Dom0 with 'debug' appended to grub. xl-dmesg > with log_lvl=all guest_loglvl=all set. Please let me know if there are > other logs or log levels that I should provide. The native kernel log supports there only being a single interrupt in use. I'm still not seeing any proof of your claim for this to be different. Did you double check lspci output in the native case? Jan Jan, 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? 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+ 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+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci cat /boot/config-3.18.1-1.fc20.x86_64 | grep XHCI CONFIG_USB_XHCI_HCD=y CONFIG_USB_XHCI_PCI=y _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |