From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH, RFC] x86: make the GDT per-CPU
Date: Thu, 11 Sep 2008 14:15:51 +0100
Message-ID: <C4EED897.26F87%keir.fraser@eu.citrix.com>
References: <48C92E69.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <48C92E69.76E4.0078.0@novell.com>
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: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 11/9/08 13:42, "Jan Beulich" <jbeulich@novell.com> wrote:

>> No, this would break 32-bits at least: The GDT entry for the selector
>> loaded into TR must remain a valid, busy TSS descriptor for the whole
>> lifetime of the system. So it can't be shared with the LDT. But even for
>> 64-bits I would fear using the same GDT slot for both LDT and GDT
>> loading.
> 
> Actually, there's a second aspect here, too (again for 32-bits): As a
> follow-up patch I'm planning to make the double fault TSS per-CPU, too.
> This wasn't as simple with the global GDT as it would be with the per-CPU
> one.

Well, the extra LGDT looks like it will take about 130 cycles on Core-2
hardware. I suppose that is tolerable.

 -- Keir