From: Eli Cohen <eli@dev.mellanox.co.il>
To: Jan Beulich <JBeulich@suse.com>
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, 5 Oct 2011 11:00:48 +0200 [thread overview]
Message-ID: <20111005090048.GD2681@mtldesk30> (raw)
In-Reply-To: <4E8C369E020000780005967C@nat28.tlf.novell.com>
On Wed, Oct 05, 2011 at 09:51:10AM +0100, Jan Beulich wrote:
>
> 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.
>
Thanks.
>
> 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.
>
I think I used the wrong terminology not distinguishing between the
hypervisor and dom0 so I will ask again just to make sure. Is the
hypervisor involved in passing the interrupts? Does it depend on
whether the guest is paravirtualized or not? The guest I am using is
paravirtualized (i.e uses xen hypercalls), so does it mean that it
uses event channels or is there a possibilty that it does not use
event channels.
next prev parent reply other threads:[~2011-10-05 9:00 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
2011-10-05 9:00 ` Eli Cohen [this message]
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=20111005090048.GD2681@mtldesk30 \
--to=eli@dev.mellanox.co.il \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--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.