From: Chris Wright <chrisw@osdl.org>
To: Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
Cc: "Magenheimer,
Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
Chris Wright <chrisw@osdl.org>,
xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen
Date: Wed, 18 May 2005 09:53:31 -0700 [thread overview]
Message-ID: <20050518165331.GS27549@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050518101515.GA22028@snarc.org>
* Vincent Hanquez (vincent.hanquez@cl.cam.ac.uk) wrote:
> On Tue, May 17, 2005 at 11:14:35AM -0700, Chris Wright wrote:
> > [snip]
>
> So let's recap:
>
> xen arch code in arch/$(ARCH)/mach-xen/
> xen generic code in drivers/xen/core/
> xen arch includes in include/asm-$(ARCH)/mach-xen/
> xen generic includes in include/asm-xen/
>
> Now for arch that don't use mach-XX syntax we can probably make a
> xen directory instead of a mach-xen directory, but I'ld rather go with
> something consistant.
yes, it needs to be consistant, partly just for ease of working with
kbuild (otherwise we rebuild an unnecessary infrastructure). Andi, for
example, was open to the idea of adding sub-arch to x86_64 to support
xen. He just hadn't needed sub-arch support yet.
> As well we can probably host a public tree in cambridge for anybody
> interested in the files reorganisation.
>
> Any others thought, comments ?
Do you have a list of more of the consolidation/cleanups like the
user_mode/user_mode_vm bits that you sent upstream?
next prev parent reply other threads:[~2005-05-18 16:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 18:09 linux/arch/xen/i386 or linux/arch/i386/xen Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 18:14 ` Chris Wright
2005-05-18 10:15 ` Vincent Hanquez
2005-05-18 16:53 ` Chris Wright [this message]
2005-05-18 18:56 ` Vincent Hanquez
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 17:18 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-19 18:55 ` Chris Wright
2005-05-18 19:21 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 17:00 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 17:17 ` Chris Wright
2005-05-18 18:35 ` Zachary Amsden
2005-05-18 15:09 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-18 16:47 ` Chris Wright
2005-05-18 19:00 ` Vincent Hanquez
2005-05-18 19:48 ` Zachary Amsden
2005-05-18 20:31 ` Vincent Hanquez
2005-05-17 19:05 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 17:25 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-17 17:58 ` Chris Wright
2005-05-18 18:20 ` Christian Limpach
2005-05-16 22:42 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 22:50 ` Mark Williamson
2005-05-16 23:22 ` Chris Wright
2005-05-16 21:37 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 22:21 ` Mark Williamson
2005-05-16 17:36 Magenheimer, Dan (HP Labs Fort Collins)
2005-05-16 18:07 ` Chris Wright
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=20050518165331.GS27549@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=dan.magenheimer@hp.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=vincent.hanquez@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.