From: "Jan Beulich" <JBeulich@suse.com>
To: Eli Cohen <eli@dev.mellanox.co.il>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen interrupts when using passthrough
Date: Wed, 05 Oct 2011 08:27:07 +0100 [thread overview]
Message-ID: <4E8C22EB0200007800059622@nat28.tlf.novell.com> (raw)
In-Reply-To: <20111004190034.GA19881@mtldesk30>
>>> On 04.10.11 at 21:00, Eli Cohen <eli@dev.mellanox.co.il> wrote:
> Here's a description. I have a PCI device which supports SRIOV, so
> there are several virtual functions besides the primary function. The
> device generates interrupts using MSI-X. I bind one of the virtual
> functions to the guest. The PCI device driver at the guest requests
> msix vectors from kernel and gets two vectors. Then it calls
> request_irq for those vectors.
> When the device generates msix interrupt using the address/data in
> it's msi-x table. However, the guest kernel complains the no handler
> is registered for this vector. Specifically, I request_irq for vectors
> 48 and 49. When the device issues interrupt for vector 49, the guest
> complains that it received interrupt for vector 89 which has no
> handler routine.
Quite possibly a mixup of Xen and Linux IRQ numbers. You may want
to check Xen's 'i' and 'e' debug key output for whether this might be
the case.
> My geust kernel is 2.6.32 based
Upstream (pv-ops), forward-port (most likely SUSE-derived), HVM, or
yet something else?
> and I can't see any file with the name
> event_channel.c.
That's a hypervisor source file, not a Linux one.
Jan
next prev parent reply other threads:[~2011-10-05 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 16:29 Xen interrupts when using passthrough Eli Cohen
2011-10-04 16:50 ` Andrew Cooper
2011-10-04 19:00 ` Eli Cohen
2011-10-05 7:27 ` Jan Beulich [this message]
2011-10-05 8:26 ` Eli Cohen
2011-10-05 8:51 ` Jan Beulich
2011-10-05 9:00 ` Eli Cohen
2011-10-05 9:09 ` Jan Beulich
2011-10-05 9:45 ` Eli Cohen
2011-10-05 9:54 ` Ian Campbell
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=4E8C22EB0200007800059622@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=eli@dev.mellanox.co.il \
--cc=xen-devel@lists.xensource.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.