From owner-freebsd-arch@FreeBSD.ORG Tue May 29 05:44:49 2007 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9381316A4C0; Tue, 29 May 2007 05:44:49 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1-b.corp.dcn.yahoo.com (mrout1-b.corp.dcn.yahoo.com [216.109.112.27]) by mx1.freebsd.org (Postfix) with ESMTP id 60B3713C447; Tue, 29 May 2007 05:44:49 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1-b.corp.dcn.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id l4T5YPMY007660; Mon, 28 May 2007 22:34:26 -0700 (PDT) Date: Tue, 29 May 2007 10:55:54 +0900 Message-ID: From: gnn@freebsd.org To: Rink Springer In-Reply-To: <20070528130101.GD48357@rink.nu> References: <20070528130101.GD48357@rink.nu> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.95 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: arch@freebsd.org Subject: Re: FreeBSD/xen structure X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 05:44:49 -0000 At Mon, 28 May 2007 15:01:01 +0200, Rink Springer wrote: > > Hi everyone, > > As I've just mailed to current@, work is well underway on the Xen > porting effort. However, as not only I but a lot of people will want to > see this work integrated into CURRENT at some point, I'd like to raise a > discussion on the directory layout I'm using. It has not changed from > Kip Macy's perforce tree, but I want to ensure that this will be > suitable for inclusion in the tree. > > Basically, i386-xen (it's i386 only for now) is a sub-architecture just > like pc98. The layout is the following: > > i386-xen/ Xen main tree > compile/ Compile tree > conf/ Kernel configs > i386-xen/ Low-level code, comparable to i386/i386/ > include/ Include files - most include their i386/include/ > version, but some are different or extended. > > This is basically the machine-dependant stuff. Should a port of amd64-xen > happen in the future, it would go using a simular directory layout. > > Xen-dependant but architecture-independant drivers (such as the Xen > block device drivers) are put in the dev/xen directory. It should be > possible to use these drivers in a amd64-xen version as well. > > I'd prefer to keep Xen in a i386-xen tree, as there are quite a lot of > changes, comparable to the amd64 <-> i386 split. And I am sure we are > not really in favour for douzens of #ifdef XEN's in the tree. > > Are there any questions, comments, remarks etc. on this layout? You can > inspect the work in perforce (//projects/xen3); currently, none of my > changes have been committed, but the layout is the same. This looks correct to me, and I think following the pc98 "sub-architecture" model is the right way to go. Thanks for working on this! Please let us know when it's ready to play with. Thanks, George