Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751039AbVLLCcy (ORCPT ); Sun, 11 Dec 2005 21:32:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751040AbVLLCcy (ORCPT ); Sun, 11 Dec 2005 21:32:54 -0500 Received: from fsmlabs.com ([168.103.115.128]:59866 "EHLO spamalot.fsmlabs.com") by vger.kernel.org with ESMTP id S1751038AbVLLCcx (ORCPT ); Sun, 11 Dec 2005 21:32:53 -0500 X-ASG-Debug-ID: 1134354771-4076-73-0 X-Barracuda-URL: http://10.0.1.244:8000/cgi-bin/mark.cgi Date: Sun, 11 Dec 2005 18:38:23 -0800 (PST) From: Zwane Mwaikambo To: Ravikiran G Thirumalai cc: Andi Kleen , Rohit Seth , Andrew Morton , linux-kernel@vger.kernel.org, discuss@x86-64.org, zach@vmware.com, shai@scalex86.org, nippung@calsoftinc.com X-ASG-Orig-Subj: Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary Subject: Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary In-Reply-To: Message-ID: References: <20051208215514.GE3776@localhost.localdomain> <1134083357.7131.21.camel@akash.sc.intel.com> <20051208231141.GX11190@wotan.suse.de> <1134084367.7131.32.camel@akash.sc.intel.com> <20051208232610.GY11190@wotan.suse.de> <1134085511.7131.53.camel@akash.sc.intel.com> <20051208234320.GB11190@wotan.suse.de> <20051209221922.GA3676@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=5.0 KILL_LEVEL=5.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.6203 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 835 Lines: 23 On Sun, 11 Dec 2005, Zwane Mwaikambo wrote: > On Fri, 9 Dec 2005, Ravikiran G Thirumalai wrote: > > > > For the BP case it's ok as > > > long as the beginning is correctly aligned and the rest > > > is read-only. > > > > Just that any writes on the bp GDT will invalidate the idt_table cacheline, > > which is read mostly (as Nippun pointed out). So could we keep the padding > > as it is for the BP too? > > But how often is this occuring? I presume this is for the virtualisation > case only? Ignore this it's a misfire from an old postponed message (i saw the reply by Andi). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/