From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1424029AbWKIPaL (ORCPT ); Thu, 9 Nov 2006 10:30:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1424054AbWKIPaL (ORCPT ); Thu, 9 Nov 2006 10:30:11 -0500 Received: from gwmail.nue.novell.com ([195.135.221.19]:30171 "EHLO emea5-mh.id5.novell.com") by vger.kernel.org with ESMTP id S1424029AbWKIPaJ (ORCPT ); Thu, 9 Nov 2006 10:30:09 -0500 Message-Id: <455357C9.76E4.0078.0@novell.com> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Thu, 09 Nov 2006 16:31:05 +0100 From: "Jan Beulich" To: "Steven Rostedt" , "Andi Kleen" Cc: , , "LKML" Subject: [Xen-devel] Re: [PATCH] shorten the x86_64 boot setup GDT to what the comment says References: <200611091413.21415.ak@suse.de> In-Reply-To: <200611091413.21415.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>> Andi Kleen 09.11.06 14:13 >>> > >> Stephen Tweedie has written up a patch to fix the Xen side and will be >> submitting that to those folks. But that doesn't excuse the GDT limit >> being a magnitude too big. > >Added thanks Once at this - why not set it to the *correct* value, just like i386 does, and update the comment at once? Namely, why would you expect to never run into the original problem again if there are still possible selectors pointing into invalid, yet within limits parts of the GDT? Jan