WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Mini-OS and force_evtchn_callback()

To: Simon Kagstrom <simon.kagstrom@xxxxxx>
Subject: Re: [Xen-devel] Mini-OS and force_evtchn_callback()
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 27 Jan 2006 14:41:24 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 27 Jan 2006 14:44:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060127142748.GH11924@xxxxxxxxxxxxxxxxx>
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: <20060127142748.GH11924@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 27 Jan 2006, at 14:27, Simon Kagstrom wrote:

I'm trying to understand the event channel handling more in detail, and was playing around a bit with the Mini-OS. However, it does not behave quite as
I had expected.

After having done a sti(), I do a force_evtchn_callback() which I though would cause an event to be sent to hypervisor_callback(), which was registered as
the channel callback with HYPERVISOR_set_callacks().

It'll only force a callback if an event is pending.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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