From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [GIT PULL] Xen updates
Date: Wed, 27 Oct 2010 12:29:32 -0700 [thread overview]
Message-ID: <4CC87D9C.3070908@goop.org> (raw)
In-Reply-To: <1858642776.20101027212236@eikelenboom.it>
On 10/27/2010 12:22 PM, Sander Eikelenboom wrote:
> Yes this enables the msi(-x) interrupts ! Thanks
> I will give the problem with the bios option another try as well.
>
> What i was wondering .. though ..
> Devices using normal interrupts generally get a low IRQ number
> Devices with MSI a higher, but MSI-X seem to get a low IRQ number as well, is this expected ?
I think that's showing you what gsi you would get if you weren't using
msi. What does /proc/interrupts show?
J
next prev parent reply other threads:[~2010-10-27 19:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 23:45 [GIT PULL] Xen updates Jeremy Fitzhardinge
2010-10-27 8:56 ` Sander Eikelenboom
2010-10-27 9:13 ` Ian Campbell
2010-10-27 9:50 ` Sander Eikelenboom
2010-10-27 10:42 ` Stefano Stabellini
2010-10-27 15:29 ` Sander Eikelenboom
2010-10-27 17:15 ` Stefano Stabellini
2010-10-27 17:22 ` Stefano Stabellini
2010-10-27 17:34 ` Stefano Stabellini
2010-10-27 19:22 ` Sander Eikelenboom
2010-10-27 19:29 ` Jeremy Fitzhardinge [this message]
2010-10-27 19:40 ` Sander Eikelenboom
2010-10-27 20:05 ` Jeremy Fitzhardinge
2010-10-27 20:15 ` Sander Eikelenboom
-- strict thread matches above, loose matches on Subject: below --
2010-11-22 20:31 Jeremy Fitzhardinge
2010-11-22 20:31 ` Jeremy Fitzhardinge
2010-08-04 22:15 Jeremy Fitzhardinge
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=4CC87D9C.3070908@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=stefano.stabellini@eu.citrix.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.