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

[Xen-devel] hypercall execution path?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] hypercall execution path?
From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
Date: Thu, 22 Feb 2007 12:17:34 -0500
Delivery-date: Thu, 22 Feb 2007 09:16:57 -0800
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: Thunderbird 3.0a1 (Macintosh/20061221)
I'm trying to trace the execution path taken by the system when I make a hypercall from a domU kernel. What I'm seeing in the hypercall entry function in Xen is that the domU eip value points to a location in the domU hypercall page for the __HYPERCALL_sched_op hypercall, even though this is *not* the hypercall that I just called.

Could someone help clarify this for me? Why would the vcpu for the guest domain have this seemingly incorrect eip value?

Thanks,
bryan

-
Bryan D. Payne
Graduate Student, Computer Science
Georgia Tech Information Security Center
http://www.bryanpayne.org

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

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