From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mathieu Ropert <mro@adviseo.fr>
Subject: [RFC] event channels and xen callbacks
Date: Tue, 04 Apr 2006 18:10:11 +0200
Message-ID: <44329A63.2020808@adviseo.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hi,

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

Regards,

Mathieu