From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: RE: [RFC] [PATCH] Dom0: Don't switch back to user space
	stack in syscall entry
Date: Fri, 12 Feb 2010 08:16:14 +0000
Message-ID: <4B751C5E020000780002F306@vpn.id2.novell.com>
References: <C8EDE645B81E5141A8C6B2F73FD9265117C58A35FD@shzsmsx501.ccr.corp.intel.com>
	<4B72F72F.3080107@goop.org>
	<4B73D3A7020000780002EE6D@vpn.id2.novell.com>
	<C8EDE645B81E5141A8C6B2F73FD926511BFBA580CF@shzsmsx501.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD926511BFBA580CF@shzsmsx501.ccr.corp.intel.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Yunhong Jiang <yunhong.jiang@intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Keir Fraser <keir.fraser@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

>>> "Jiang, Yunhong" <yunhong.jiang@intel.com> 12.02.10 05:30 >>>
>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.

For the specific syscall case there probably aren't (but I didn't fully
think this through). But for the general case there are, so if IST-like
support is to be added, it should account for nesting.

Jan