From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: linux/arch/xen/i386 or linux/arch/i386/xen Date: Wed, 18 May 2005 09:53:31 -0700 Message-ID: <20050518165331.GS27549@shell0.pdx.osdl.net> References: <516F50407E01324991DD6D07B0531AD542CDB3@cacexc12.americas.cpqcorp.net> <20050517181435.GH27549@shell0.pdx.osdl.net> <20050518101515.GA22028@snarc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20050518101515.GA22028@snarc.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vincent Hanquez Cc: "Magenheimer, Dan (HP Labs Fort Collins)" , Chris Wright , xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.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?