From: David Vrabel <david.vrabel@citrix.com>
To: Justin Acker <ackerj67@yahoo.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xhci_hcd intterrupt affinity in Dom0/DomU limited to single interrupt
Date: Wed, 2 Sep 2015 14:47:05 +0100 [thread overview]
Message-ID: <55E6FDD9.1090301@citrix.com> (raw)
In-Reply-To: <631331126.1156575.1441129186888.JavaMail.yahoo@mail.yahoo.com>
On 01/09/15 18:39, Justin Acker wrote:
> Taking this to the dev list from users.
>
> Is there a way to force or enable pirq delivery to a set of cpus as
> opposed to single device from being a assigned a single pirq so that its
> interrupt can be distributed across multiple cpus?
No.
PIRQs are delivered via event channels and these can only be bound to
one VCPU at a time.
David
next prev parent reply other threads:[~2015-09-02 13:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441121643.26292.63.camel@citrix.com>
[not found] ` <800613365.4285959.1441128848192.JavaMail.yahoo@mail.yahoo.com>
2015-09-01 17:39 ` xhci_hcd intterrupt affinity in Dom0/DomU limited to single interrupt 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 [this message]
2015-09-02 17:25 ` Justin Acker
2015-09-02 17:35 ` David Vrabel
[not found] <55E6C83402000078000D7CF5@prv-mh.provo.novell.com>
[not found] ` <1981596850.505327.1441214239184.JavaMail.yahoo@mail.yahoo.com>
2015-09-03 10:15 ` 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
2015-09-21 12:53 ` Jan Beulich
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=55E6FDD9.1090301@citrix.com \
--to=david.vrabel@citrix.com \
--cc=ackerj67@yahoo.com \
--cc=xen-devel@lists.xen.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).