This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] ia64 event channels

To: Arun Sharma <arun.sharma@xxxxxxxxx>
Subject: Re: [Xen-devel] ia64 event channels
From: Matt Chapman <matthewc@xxxxxx>
Date: Tue, 14 Jun 2005 18:50:48 -0600
Cc: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 15 Jun 2005 00:49:52 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42AF578C.6030105@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20050614203243.GA31485@xxxxxxxxxxxxxxx> <mailman.1118781182.16413@xxxxxxxxxxxxxxxxxxxx> <42AF578C.6030105@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Jun 14, 2005 at 03:17:48PM -0700, Arun Sharma wrote:
> 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.

Ah, I hadn't seen that patch.  In that case, it is indeed better
to abstract what I added to evtchn.h behind a hook function like

I think this hook should be relevant for x86 VMX as well?  i.e.  if
we arrange it so that vmx_check_guest_event is called from
evtchn_set_pending, then you don't have to call it on every exit to

> Also, it might be good to unify the names (callback_irq vs evtchn_vector 
> -- I like evtchn_vector better).

Sure.  Also, I put it in the shared_info; I'm happy to move it to the
VCPU structure though, that may be more appropriate.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>