From: Chris Wright <chrisw@osdl.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
"Martin J. Bligh" <mbligh@mbligh.org>,
linux-kernel@vger.kernel.org,
Pratap Subrahmanyam <pratap@vmware.com>
Subject: Re: [PATCH] abstract out bits of ldt.c
Date: Sun, 7 Aug 2005 18:08:28 -0700 [thread overview]
Message-ID: <20050808010828.GU7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <42F6AF8E.60107@vmware.com>
* 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.
> I think introducing mach-xen headers is a bit premature though - lets
> get the interface nailed down first so that the hypervisor developers
> have time to settle the include/asm-i386/mach-xxx files without dealing
> unneeded churn onto the maintainers.
I don't think there's any point in putting mach-xen stuff in either.
Can we please discuss these patches in some sane way (say on the
virutalization list) so we're not cross-firing at each other. It's just
going to be too messy otherwiswe.
thanks,
-chris
next prev parent reply other threads:[~2005-08-08 1:08 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 [this message]
2005-08-08 1:16 ` Zachary Amsden
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=20050808010828.GU7762@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pratap@vmware.com \
--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