[Xen-ia64-devel] Re: "current->domain" points to wrong domain after domU launch

[Haavard Bjerke <havard.bjerke@xxxxxxx>]

It was in fact dom1 doing the hypercall. Sorry for the false alarm.

Haavard

On Mon, May 30, 2005 at 11:23:44AM -0700, Magenheimer, Dan (HP Labs Fort 
Collins) wrote:
> Sorry for the late reply.  This is a holiday weekend in the U.S.
> 
> I am surprised by your result as I have never seen anything
> other than domain_id==0 for dom0.
> 
> Current is in r13 when Xen is active and is saved in ar.k6
> when a domain is running.  (This is the same as Linux and,
> indeed, the code used to manage this is virtually identical
> to Linux kernel entry/exit code. 
> 
> > -----Original Message-----
> > From: Haavard Bjerke [mailto:havard.bjerke@xxxxxxx] 
> > Sent: Saturday, May 28, 2005 8:13 AM
> > To: Magenheimer, Dan (HP Labs Fort Collins)
> > Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: "current->domain" points to wrong domain after domU launch
> > 
> > After launching domU, current->domain->domain_id is 1, even 
> > right after executing a hypercall from dom0. To get this 
> > result, I placed the following line in a hypercall in hypercall.c:
> > 
> > printk("hypercall.c: current domain is %d\n", 
> > current->domain->domain_id);
> > 
> > It printed "(XEN) hypercall.c: current domain is 1", though 
> > dom0 executed the hypercall.
> > 
> > This is not the way it behaves in the x86 version, where 
> > current->domain will point to dom0.
> > 
> > There's no "set_current()" in Xen/ia64; how is "current" maintained?
> > 
> > Haavard
> > 

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