From: Arun Sharma <arun.sharma@intel.com>
To: Matt Chapman <matthewc@hp.com>
Cc: "Ling, Xiaofeng" <xiaofeng.ling@intel.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: ia64 event channels
Date: Tue, 14 Jun 2005 15:17:48 -0700 [thread overview]
Message-ID: <42AF578C.6030105@intel.com> (raw)
In-Reply-To: <mailman.1118781182.16413@unix-os.sc.intel.com>
Matt Chapman wrote:
> This is the one change we've made to architecture-independent code
> for event channels. Rather than polling the event channel flags
> on every return, we pend an interrupt in evtchn_set_pending.
>
> This might be better abstracted into some architecture-dependent
> header file, but I'm not sure where. We could add an asm/event.h,
> though it does seem a bit excessive to add a file just for one
> trivial hook.
Not all event channel events get injected into the guest. For eg, on
VT-x and VT-i, we use event channels to communicate events from the
device models to the hypervisor on handling memory mapped and accesses
to I/O ports.
Have you already looked at this patch:
http://article.gmane.org/gmane.comp.emulators.xen.devel/10852
vmx_check_guest_event() does something very similar.
Also, it might be good to unify the names (callback_irq vs evtchn_vector
-- I like evtchn_vector better).
-Arun
next prev parent reply other threads:[~2005-06-14 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 20:32 ia64 event channels Matt Chapman
[not found] ` <mailman.1118781182.16413@unix-os.sc.intel.com>
2005-06-14 22:17 ` Arun Sharma [this message]
2005-06-15 0:50 ` Matt Chapman
2005-06-15 19:29 ` [PATCH] " Matt Chapman
2005-06-15 20:15 ` Arun Sharma
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=42AF578C.6030105@intel.com \
--to=arun.sharma@intel.com \
--cc=matthewc@hp.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiaofeng.ling@intel.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.