From owner-freebsd-arch@FreeBSD.ORG Tue May 29 05:55:48 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 91F5416A549; Tue, 29 May 2007 05:55:48 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 476A213C448; Tue, 29 May 2007 05:55:48 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4T5svvS025363; Mon, 28 May 2007 23:54:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 23:55:13 -0600 (MDT) Message-Id: <20070528.235513.420517798.imp@bsdimp.com> To: rink@freebsd.org From: "M. Warner Losh" In-Reply-To: <20070528130101.GD48357@rink.nu> References: <20070528130101.GD48357@rink.nu> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 23:54:57 -0600 (MDT) 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:55:48 -0000 In message: <20070528130101.GD48357@rink.nu> Rink Springer writes: : 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. How pervasive are these diffs? And to what extent are you able to reuse the i386 stuff? Can you characterize, say, the number of lines and/or files that would be affected if you went the ifdef route? It sounds like the tree is right, but that has its own cost and shouldn't be undertaken lightly. : 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. I like the layout, assuming it is needed. Warner