From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ben Catterall <Ben.Catterall@citrix.com>
Subject: Re: [RFC 3/4] HVM x86 deprivileged mode: Code for
 switching into/out of deprivileged mode
Date: Tue, 18 Aug 2015 11:26:52 +0100
Message-ID: <55D3086C.2020701@citrix.com>
References: <20150810094928.GC3094@deinos.phlegethon.org>
	<55C87989.6050700@citrix.com>
	<20150811095535.GA884@deinos.phlegethon.org>
	<55CA2824.4020405@citrix.com>
	<20150811170522.GD884@deinos.phlegethon.org>
	<55CA2E91.4030204@citrix.com> <55CA3EF3.7090001@oracle.com>
	<55CB4A56.1000600@citrix.com> <55CB4B14.8060704@citrix.com>
	<55D1E770.5070906@citrix.com>
	<20150817150713.GB42311@deinos.phlegethon.org>
	<55D21719020000780009B6BB@prv-mh.provo.novell.com>
	<55D30826.4030309@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <55D30826.4030309@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xensource.com, keir@xen.org, ian.campbell@citrix.com, george.dunlap@eu.citrix.com, Andrew Cooper <andrew.cooper3@citrix.com>, Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>, Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>
List-Id: xen-devel@lists.xenproject.org



On 18/08/15 11:25, Ben Catterall wrote:
>
>
> On 17/08/15 16:17, Jan Beulich wrote:
>>>>> On 17.08.15 at 17:07, <tim@xen.org> wrote:
>>> At 14:53 +0100 on 17 Aug (1439823232), Ben Catterall wrote:
>>>> So, have we arrived at a decision for this? Thanks!
>>>
>>> Seems to have stalled a bit.  OK, I propose that:
>>>   - we use TR/IST to make Xen take interrupts/exceptions at a
>>> different SP;
>>>   - we make that SP be an extension of the main stack, so that things
>>>     like current() Just Work[tm];
>  From Xen's cpu stack layout, page 4 is currently unused so I'll put it
> here. Is this an acceptable?
Or, would it be better to put it at position 5, and move the optional 
MEMORY_GUARD page down to position 4?
>>>   - we set this up and tear it down when we enter/leave depriv mode.
>>>   - someone ought to look at the case where IST handlers copy
>>>     themselves to the main stack, and see if we need to adjust that too.
>>>
>>> Any other proposals?
>>
>> No.
>>
>
>
>>> I think we can leave the question of TR switching on VMEXIT as a
>>> separate issue.
>>
>> Just like for the other one - at this point I think anything that work
>> should be okay. Dealing with quirks can be deferred (but it would
>> be nice if a respective note was added in a prominent place so it
>> doesn't get forgotten once/if these patches leave RFC state).
>>
>> Jan
>>
> Ok, thanks all!