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] Re: Xen: Hybrid extension patchset for hypervisor

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 16 Sep 2009 14:22:15 -0700
Cc: "Yang, Sheng" <sheng.yang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Delivery-date: Wed, 16 Sep 2009 14:22:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1253135571.3896.4873.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <C6D66994.14D6A%keir.fraser@xxxxxxxxxxxxx> <C6D6AEEA.14EBF%keir.fraser@xxxxxxxxxxxxx> <0B53E02A2965CE4F9ADB38B34501A3A1940C78A8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4AB12C1F.9080502@xxxxxxxx> <1253135571.3896.4873.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 09/16/09 14:12, Ian Campbell wrote:
>>> Based on our data, what we would want in PV 64-bit guests are, 
>>> fundamentally:
>>> - have the kernel run in ring 0 (so that it can regain the performance 
>>> enhancements)
>>>   
>>>       
>> That's no problem.  PV kernels don't currently assume they're running in
>> any particular ring, so they'd be happy to run in ring 0 if that's how
>> they're started (if there are problems, I'd consider that a bug).  We
>> could then check for ring 0 and enable syscall/sysenter.
>>     
> XENFEAT_supervisor_mode_kernel is supposed to enable this behaviour,
> although it hasn't been actively used for several years and never in the
> pvops kernel so you can bet it has bit-rotted...
>   

That tends to have a slightly different meaning, viz "dom0 really *is*
privileged and can do anything it feels like".  It isn't necessary to
have a specific feature/mechanism for "kernel happens to be in ring 0";
it can look at its own cs ring number.

>> We could do that with minimal API/ABI changes by:
>>
>>     * Providing an identity p2m table
>>     * Changing the hypercall page to make pte writes simple memory
>>       writes (no hypercalls); xen would still keep track of pinned pages
>>       and trap'n'emulate on them for back-compatibility (but fast-path
>>       with no validation).  We could expose the presence of HAP via
>>       xen_features so that guests know they can avoid marking pagetables
>>       RO, etc.
>>     * Similarly, cr3 changes can be fast-pathed within the hypercall page.
>>     * Whatever else I've overlooked.
>>     
> Some combination of XENFEAT_writable_page_tables
> XENFEAT_writable_descriptor_tables and XENFEAT_auto_translated_physmap
> might be of interest for this bit.

Making use of XENFEAT_auto_translated_physmap would avoid the need for
identity p2m/m2p tables, but I'm not sure whether it still works.  I got
close to completely removing all references to it at one point, but I
think ia64 uses it?

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