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


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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Mini-OS and force_evtchn_callback()
From: Simon Kagstrom <simon.kagstrom@xxxxxx>
Date: Fri, 27 Jan 2006 15:27:48 +0100
Delivery-date: Fri, 27 Jan 2006 14:36:52 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i

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().

The callback is not called until the domain issues a HYPERVISOR_set_timer_op() 
thereafter blocks with HYPERVISOR_sched_op(). Is this the expected behavior,
or is there something wrong with the Mini-OS or did I simply miss something?

// Simon

Xen-devel mailing list

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