public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rohit Seth <rohit.seth@intel.com>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: 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: Thu, 08 Dec 2005 15:09:17 -0800	[thread overview]
Message-ID: <1134083357.7131.21.camel@akash.sc.intel.com> (raw)
In-Reply-To: <20051208215514.GE3776@localhost.localdomain>

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.
This was mainly to address the excessive cost in virtualized
environments of sharing the gdt page with other RW items in per_cpu_data
structure.  I think the padding was because xen does not like sharing
gdt page with anything else...

I agree that if no other constraint is there then IDT could be moved
into the same page.

-rohit


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 19:42 [patch] x86_64: align and pad x86_64 GDT on page boundary 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 [this message]
2005-12-08 23:11       ` Andi Kleen
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=1134083357.7131.21.camel@akash.sc.intel.com \
    --to=rohit.seth@intel.com \
    --cc=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=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