From: Justin Acker <ackerj68@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: xhci_hcd intterrupt affinity in Dom0/DomU limited to single interrupt
Date: Wed, 16 Sep 2015 16:31:53 -0400 [thread overview]
Message-ID: <1442435513.5195.8.camel@localhost> (raw)
In-Reply-To: <55F2C32202000078000A2069@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 3368 bytes --]
On Fri, 2015-09-11 at 04:03 -0600, Jan Beulich wrote:
> >>> On 10.09.15 at 18:20, <ackerj67@yahoo.com> wrote:
> > On Wed, 2015-09-09 at 00:48 -0600, Jan Beulich wrote:
> >> >>> On 08.09.15 at 18:02, <ackerj67@yahoo.com> 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
[-- Attachment #1.2: Type: text/html, Size: 5095 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-09-16 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55E6C83402000078000D7CF5@prv-mh.provo.novell.com>
[not found] ` <1981596850.505327.1441214239184.JavaMail.yahoo@mail.yahoo.com>
2015-09-03 10:15 ` xhci_hcd intterrupt affinity in Dom0/DomU limited to single interrupt Jan Beulich
2015-09-03 12:04 ` Justin Acker
2015-09-03 15:04 ` Jan Beulich
2015-09-03 16:52 ` Justin Acker
2015-09-04 7:41 ` Jan Beulich
2015-09-08 16:02 ` Justin Acker
2015-09-09 6:48 ` Jan Beulich
2015-09-10 16:20 ` Justin Acker
2015-09-11 10:03 ` Jan Beulich
2015-09-16 20:31 ` Justin Acker [this message]
2015-09-21 12:53 ` Jan Beulich
[not found] <1441121643.26292.63.camel@citrix.com>
[not found] ` <800613365.4285959.1441128848192.JavaMail.yahoo@mail.yahoo.com>
2015-09-01 17:39 ` Justin Acker
2015-09-01 20:56 ` Konrad Rzeszutek Wilk
2015-09-01 21:38 ` Boris Ostrovsky
2015-09-01 23:09 ` Justin Acker
2015-09-02 12:53 ` Konrad Rzeszutek Wilk
2015-09-02 13:49 ` Ian Campbell
2015-09-02 17:12 ` Justin Acker
2015-09-02 17:02 ` Justin Acker
2015-09-02 13:47 ` David Vrabel
2015-09-02 17:25 ` Justin Acker
2015-09-02 17:35 ` David Vrabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442435513.5195.8.camel@localhost \
--to=ackerj68@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).