From: Zachary Amsden <zach@vmware.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
"Martin J. Bligh" <mbligh@mbligh.org>,
linux-kernel@vger.kernel.org,
Pratap Subrahmanyam <pratap@vmware.com>,
virtualization@lists.osdl.org
Subject: Re: [PATCH] abstract out bits of ldt.c
Date: Sun, 07 Aug 2005 18:16:04 -0700 [thread overview]
Message-ID: <42F6B254.2090404@vmware.com> (raw)
In-Reply-To: <20050808010828.GU7762@shell0.pdx.osdl.net>
Chris Wright wrote:
>* Zachary Amsden (zach@vmware.com) wrote:
>
>
>>Does Xen assume page aligned descriptor tables? I assume from this
>>
>>
>
>Yes.
>
>
>
>>patch and snippets I have gathered from others, that is a yes, and other
>>things here imply that DT pages are not shadowed. If so, Xen itself
>>must have live segments in the GDT pages, so how do you allocate space
>>for the per-CPU GDT pages on SMP?
>>
>>
>
>early during boot.
>
>
Doesn't that require 16 pages per CPU? That seems excessive to impose
on a native build. Perhaps we could get away with 1 page per CPU for
the GDT on native boots and bump that up to 16 if compiling for a
virtualized sub-architecture - i.e. move GDT to a page aligned struct
for native (doesn't cost too much), and give it MACH_GDT_PAGES of space
which is defined by the sub-architecture.
Let's take this thread over to virtualization@lists.osdl.org as well.
Zach
next prev parent reply other threads:[~2005-08-08 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 23:20 [PATCH] abstract out bits of ldt.c Martin J. Bligh
2005-08-07 23:44 ` Chris Wright
2005-08-07 23:57 ` Martin J. Bligh
2005-08-07 23:59 ` Chris Wright
2005-08-08 0:41 ` Andrew Morton
2005-08-08 0:46 ` Chris Wright
2005-08-08 1:04 ` Zachary Amsden
2005-08-08 1:08 ` Chris Wright
2005-08-08 1:16 ` Zachary Amsden [this message]
2005-08-08 1:36 ` Chris Wright
2005-08-08 1:21 ` Martin J. Bligh
2005-08-08 0:59 ` Martin J. Bligh
[not found] ` <20050808113014.GA15165@elte.hu>
[not found] ` <20050808095755.23810b15.akpm@osdl.org>
2005-08-09 9:23 ` Ingo Molnar
2005-08-09 9:28 ` Christoph Hellwig
2005-08-08 8:41 ` Dave Hansen
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=42F6B254.2090404@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pratap@vmware.com \
--cc=virtualization@lists.osdl.org \
/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