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

Re: [Xen-devel] hypercall execution path?

On Thu, 2007-02-22 at 15:28 -0500, Bryan D. Payne wrote:
> uint32_t eip = sd->vcpu[0]->arch.guest_context.user_regs.eip;
> gdprintk(XENLOG_WARNING, "eip=0x%x", eip); 

sd is current->domain here so the guest context is saved on the stack
rather than in the domain structure. Therefore you need to use
guest_cpu_user_regs()->eip instead. I should have thought of that
before, sorry.

The context in the vcpu's arch.guest_context will be a stale left over
from the last time the domain was rescheduled, which is why it is doing
a sched_op since it was presumably just waking up from idle.

Ian.


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