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] [RFC] event channels and xen callbacks

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC] event channels and xen callbacks
From: Mathieu Ropert <mro@xxxxxxxxxx>
Date: Tue, 04 Apr 2006 18:10:11 +0200
Delivery-date: Thu, 06 Apr 2006 06:56:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: Mozilla Thunderbird 1.0.7 (X11/20051013)

i'm currently playing a bit with event channels and hypervisor callbacks, and i find myself stuck because i miss some informations. Maybe you can give me some hints:

on amd64 arch, i'd like to know about hypervisor callback: ie, stack layout when called by Xen, stack location in memory (is it using the TSS entry as hardware traps do?) and finally, about how HYPERVISOR_iret() expects to find the stack upon call (like when you used iret? or something else?).

I may write a little paper or tutorial from i've learned and didn't found in Xen doc after i get a better view of the whole thing...



Xen-devel mailing list

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