From: Rohit Seth <rohit.seth@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
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:26:07 -0800 [thread overview]
Message-ID: <1134084367.7131.32.camel@akash.sc.intel.com> (raw)
In-Reply-To: <20051208231141.GX11190@wotan.suse.de>
On Fri, 2005-12-09 at 00:11 +0100, Andi Kleen wrote:
> On Thu, Dec 08, 2005 at 03:09:17PM -0800, Rohit Seth wrote:
> >
> > 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.
>
...that padding in BP's GDT (in this and original patches) could be
because of the Xen requirements to have dedicated pages for gdt.
-rohit
next prev parent reply other threads:[~2005-12-08 23:20 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 [this message]
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=1134084367.7131.32.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 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.