From owner-freebsd-arch@FreeBSD.ORG Mon May 28 13:32:00 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 5900416A46C for ; Mon, 28 May 2007 13:32:00 +0000 (UTC) (envelope-from rink@thunderstone.rink.nu) Received: from mx1.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.freebsd.org (Postfix) with ESMTP id 0E79C13C480 for ; Mon, 28 May 2007 13:31:59 +0000 (UTC) (envelope-from rink@thunderstone.rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id 33F996D457 for ; Mon, 28 May 2007 15:01:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id we5BG582TeFD for ; Mon, 28 May 2007 15:01:01 +0200 (CEST) Received: from thunderstone.rink.nu (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.rink.nu (Postfix) with ESMTP id BF9386D433 for ; Mon, 28 May 2007 15:01:01 +0200 (CEST) Received: (from rink@localhost) by thunderstone.rink.nu (8.13.8/8.13.8/Submit) id l4SD11wc008181 for arch@FreeBSD.org; Mon, 28 May 2007 15:01:01 +0200 (CEST) (envelope-from rink) Date: Mon, 28 May 2007 15:01:01 +0200 From: Rink Springer To: arch@FreeBSD.org Message-ID: <20070528130101.GD48357@rink.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: 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: Mon, 28 May 2007 13:32:00 -0000 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. Thanks, -- Rink P.W. Springer - http://rink.nu "It is such a quiet thing, to fall. But yet a far more terrible thing, to admit it." - Darth Traya