[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC 3/4] HVM x86 deprivileged mode: Code for switching into/out of deprivileged mode
- To: "Ben Catterall" <Ben.Catterall@xxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Tue, 18 Aug 2015 08:22:23 -0600
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, keir@xxxxxxx, ian.campbell@xxxxxxxxxx, george.dunlap@xxxxxxxxxxxxx, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, Aravind Gopalakrishnan <Aravind.Gopalakrishnan@xxxxxxx>, SuraveeSuthikulpanit <suravee.suthikulpanit@xxxxxxx>, BorisOstrovsky <boris.ostrovsky@xxxxxxxxxx>
- Delivery-date: Tue, 18 Aug 2015 14:22:36 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 18.08.15 at 12:26, <Ben.Catterall@xxxxxxxxxx> wrote:
> 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@xxxxxxx> 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?
At this stage either would do. Once (if) the experiment yielded
positive results, we can still evaluate the pros and cons of either
placement.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
