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] 32bit/PAE guest on 64bit hypervisor work

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] 32bit/PAE guest on 64bit hypervisor work
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 21 Aug 2006 14:11:04 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 21 Aug 2006 05:11:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C10F5B10.1208%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44E9AF6E.76E4.0078.0@xxxxxxxxxx> <C10F5B10.1208%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> context switch entries 3,4,5,6 of the GDT. In fact entry 3 can perhaps stay
>>> as ring-1 code, and we only need to switch entries 4,5,6.
>> 
>> Hmm, that would mean per-CPU GDTs. I'm right now creating a second GDT,
>> and map into the guest's page tables the appropriate one. On a context
>> switch, the most that should be needed on top of what's done today then is
>> to flush the one page from the TLB (I didn't check that, but I suppose it's
>> a global translation).
>
>Per-CPU GDTs would be perfectly acceptable (it's only an extra page per
>CPU). But I suppose since we switch pagetables anyway on the ctxt switch
>path we may as well just have the appropriate ones mapped in each pagetable,
>and remove use of the global bit for that mapping.

Hmm, why flush the entry on systems where compatibility mode isn't used. I'd
rather keep the global flag and make the flush explicit, but conditional upon
old and new vcpu's domain having different compatibility mode settings.

Jan

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