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/
Home Products Support Community News


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

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Subject: [Xen-ia64-devel] Re: "current->domain" points to wrong domain after domU launch
From: Haavard Bjerke <havard.bjerke@xxxxxxx>
Date: Thu, 2 Jun 2005 15:46:02 +0200
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Jun 2005 13:45:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <516F50407E01324991DD6D07B0531AD542D2D0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD542D2D0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4i
It was in fact dom1 doing the hypercall. Sorry for the false alarm.


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] Re: "current->domain" points to wrong domain after domU launch, Haavard Bjerke <=