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] Question re do_switch_stack()

To: Avi Kivity <avi.kivity@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Question re do_switch_stack()
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Thu, 9 Jun 2005 07:44:56 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Jun 2005 14:44:06 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kYKyt968RKkY0x7G9QEQa4Efiymd778i8er/t6xDKx1o6V1scyMTVHGPEa8cDCUwQrdmNUWWe+0Ct02KwS0bygUVVyQH7YWcIfJxDDRobX/SA1Yzyvi8/nsI66/gy66/+hZQkzv/+2dVwZtzxMVuxmsZI9ylDUjOiWhc12yQo+c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1118328113.15004.28.camel@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>
References: <1118328113.15004.28.camel@xxxxxxxxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The stack_switch you're looking at is for setting the trap stack.

On 6/9/05, Avi Kivity <avi.kivity@xxxxxxxxxxxx> wrote:
> looking at do_stack_switch() (x86-32), I see that the switch is effected
> by moving the new stack pointer into current->arch.kernel_sp. however,
> entry.S only looks at kernel_sp in create_bounce_frame, but only if
> we're not returning into ring 1.
> 
> how then is the switch caused? obviously the call to do_stack_switch
> came from ring 1.
> 
> confused,
> Avi
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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