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 09:51:10 +0100 [thread overview]
Message-ID: <4E8C369E020000780005967C@nat28.tlf.novell.com> (raw)
In-Reply-To: <20111005082633.GC2681@mtldesk30>
>>> On 05.10.11 at 10:26, Eli Cohen <eli@dev.mellanox.co.il> wrote:
> On Wed, Oct 05, 2011 at 08:27:07AM +0100, Jan Beulich wrote:
>>
>> 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.
>
> Can you tell how this is done - sorry, I'm not a xen expert.
Either by sending the characters from the serial console (after switching
input to Xen), or by using "{xl,xm] debug-key" followed by
"{xm,xl} dmesg" to view the output.
>>
>> > 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.
>>
>
> So how do you think interrupts should reach the guest. Is it through
> event channels (i.e dom0 receives them first) or do they go directly
> to the guest with dom0 unaware that there was an interrupt?
Dom0 shouldn't get involved at all - Xen does the necessary conversion.
Dom0 may only be involved in setting things up. Whether they get
received via event channels or virtual interrupts depends on the kind
of guest.
Jan
next prev parent reply other threads:[~2011-10-05 8:51 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
2011-10-05 8:26 ` Eli Cohen
2011-10-05 8:51 ` Jan Beulich [this message]
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=4E8C369E020000780005967C@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.