WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen

To: Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen
From: Chris Wright <chrisw@xxxxxxxx>
Date: Wed, 18 May 2005 09:53:31 -0700
Cc: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, Chris Wright <chrisw@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Delivery-date: Wed, 18 May 2005 16:53:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050518101515.GA22028@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD542CDB3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20050517181435.GH27549@xxxxxxxxxxxxxxxxxxx> <20050518101515.GA22028@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
* Vincent Hanquez (vincent.hanquez@xxxxxxxxxxxx) 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?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>