mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rohit Seth <rohit.seth@intel.com>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
	Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org,
	zach@vmware.com, shai@scalex86.org, nippung@calsoftinc.com
Subject: Re: [discuss] [patch] x86_64:  align and pad x86_64 GDT on page boundary
Date: Fri, 9 Dec 2005 00:11:41 +0100	[thread overview]
Message-ID: <20051208231141.GX11190@wotan.suse.de> (raw)
In-Reply-To: <1134083357.7131.21.camel@akash.sc.intel.com>

On Thu, Dec 08, 2005 at 03:09:17PM -0800, Rohit Seth wrote:
> On Thu, 2005-12-08 at 13:55 -0800, Ravikiran G Thirumalai wrote:
> > On Thu, Dec 08, 2005 at 09:15:18PM +0100, Andi Kleen wrote:
> > > On Thu, Dec 08, 2005 at 11:42:32AM -0800, Ravikiran G Thirumalai
> > wrote:
> > > > 
> > > > -   .align  L1_CACHE_BYTES
> > > > +   /* zero the remaining page */
> > > > +   .fill PAGE_SIZE / 8 - GDT_ENTRIES,8,0
> > > > +  
> > > >  ENTRY(idt_table)  
> > >
> > > Why can't the IDT not be shared with the GDT page? It should be
> > mostly
> > > read only right and putting r-o data on that page should be ok,
> > right?
> > 
> > Yes, you are right.  This should not have been a problem. 
> > Some people reported this symbol (cpu_gdt) though.  Will have to go
> > back and
> > check.
> 
> IIRC, Zach's patches for gdt alignment, moved the gdts from per_cpu data
> structure to each secondary CPU dynamically allocating page for its gdt.

Kiran's patch does this too.  Except for the BP GDT, which could
be shared with the single IDT.

-Andi (who actually plans to attack per CPU IDTs at some point
so this could change later) 


  reply	other threads:[~2005-12-08 23:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 19:42 Ravikiran G Thirumalai
2005-12-08 20:15 ` [discuss] " Andi Kleen
2005-12-08 21:55   ` Ravikiran G Thirumalai
2005-12-08 23:09     ` Rohit Seth
2005-12-08 23:11       ` Andi Kleen [this message]
2005-12-08 23:26         ` Rohit Seth
2005-12-08 23:26           ` Andi Kleen
2005-12-08 23:45             ` Rohit Seth
2005-12-08 23:43               ` Andi Kleen
2005-12-09 22:19                 ` Ravikiran G Thirumalai
2005-12-09 22:57                   ` Andi Kleen
2005-12-09 23:01                   ` Rohit Seth
2005-12-09 22:59                     ` Andi Kleen
2005-12-09 23:46                       ` Ravikiran G Thirumalai
2005-12-12  2:34                   ` Zwane Mwaikambo
2005-12-12  2:31                     ` Andi Kleen
2005-12-12  2:38                     ` Zwane Mwaikambo
2005-12-08 23:50               ` Rohit Seth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051208231141.GX11190@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nippung@calsoftinc.com \
    --cc=rohit.seth@intel.com \
    --cc=shai@scalex86.org \
    --cc=zach@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®