From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Bryan D. Payne" <bryan@thepaynes.cc>
Subject: hypercall execution path?
Date: Thu, 22 Feb 2007 12:17:34 -0500
Message-ID: <45DDD02E.40007@thepaynes.cc>
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

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