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

[Xen-devel] RE: [RFC] [PATCH] Dom0: Don't switch back to user space stac

To: Jan Beulich <JBeulich@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] RE: [RFC] [PATCH] Dom0: Don't switch back to user space stack in syscall entry
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Fri, 12 Feb 2010 12:30:15 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 11 Feb 2010 20:33:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B73D3A7020000780002EE6D@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C8EDE645B81E5141A8C6B2F73FD9265117C58A35FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B72F72F.3080107@xxxxxxxx> <4B73D3A7020000780002EE6D@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acqq97rMW21Sej2ZQkaBrB1OTC+JOQAncdIw
Thread-topic: [RFC] [PATCH] Dom0: Don't switch back to user space stack in syscall entry

>-----Original Message-----
>From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx]
>Sent: Thursday, February 11, 2010 4:54 PM
>To: Jeremy Fitzhardinge; Jiang, Yunhong
>Cc: Keir Fraser; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [RFC] [PATCH] Dom0: Don't switch back to user space stack in 
>syscall
>entry
>
>>>> Jeremy Fitzhardinge <jeremy@xxxxxxxx> 10.02.10 19:13 >>>
>>> b) Add IST support to xen hypervisor, Considering the ptrace issue in
>http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00200.html and
>also Ingo's comments in
>http://lkml.indiana.edu/hypermail/linux/kernel/0905.1/00087.html, maybe it 
>still
>have value to add such support. But not sure if that is accepetable for xen
>hypervisor.
>>>
>>
>>That would depend on Keir's thoughts, which I would guess depend on what
>>the patch and ABI would look like.  It's certainly the most general
>>solution if it can be done in a reasonable way.
>
>But if at all, I'd recommend considering a properly nesting solution
>rather than just to mimic hardware behavior (since there's no IDT,
>functionality needs to differ from native anyway).

Are there any issue currently for nesting interrupt? The issue here is because 
of the syscall's stack, which is not strictly related to nesting interrupt, I 
think.

--jyh

>
>Jan


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