All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Andi Kleen <ak@suse.de>
Cc: Rohit Seth <rohit.seth@intel.com>, 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 15:46:12 -0800	[thread overview]
Message-ID: <20051209234612.GB3676@localhost.localdomain> (raw)
In-Reply-To: <20051209225921.GO11190@wotan.suse.de>

On Fri, Dec 09, 2005 at 11:59:21PM +0100, Andi Kleen wrote:
> On Fri, Dec 09, 2005 at 03:01:27PM -0800, Rohit Seth 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? 
> > > 
> > 
> > Do you write into GDT often for this to be an issue.  The reason I'm
> 
> The context switch writes into the GDT to switch around the TLS segments

Yup.

> 
> > asking this because the per-cpu IDTs that Andi refered in the future.
> > If we are really not using too many bytes in GDT then rest of the page
> > can be used for IDT and such mostly RO data.
> 
> Once I implement that it can be shared with that page.

Yes, that will be nice.

Thanks,
Kiran

  reply	other threads:[~2005-12-09 23:46 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
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 [this message]
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=20051209234612.GB3676@localhost.localdomain \
    --to=kiran@scalex86.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.