From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: new repo layout? Date: Thu, 31 May 2007 11:02:05 -0500 Message-ID: <1180627325.16734.26.camel@basalt> References: <20070530214638.GA21589@fc.hp.com> <1180598644.29571.57.camel@localhost.localdomain> Reply-To: Hollis Blanchard Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1180598644.29571.57.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: Aron Griffis , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, 2007-05-31 at 09:04 +0100, Ian Campbell wrote: > On Wed, 2007-05-30 at 17:46 -0400, Aron Griffis wrote: > > Could somebody at XenSource comment on the details of the planned repo > > changes, i.e. how things will work in the non-sparse world? For > > example, what header files will live in the HV vs. the kernel? > > Will the HV, tools, kernel typically be built simultaneously as they > > are now, or will they be built separately? > > From the point of view of someone who has cloned xen-unstable.hg and run > "make world/dist/etc" there should be no difference in what gets built. > The current tarball download+unpack+patch+sparse phases will simply be > replaced by an hg clone phase. There are already options to build other > trees as well, i.e. "make linux-2.6-paravirt-build" will build the > latest release of the paravirt_ops tree with Xen support from > http://xenbits.xensource.com/ext/paravirt_ops/ > > Each OS tree is expected to carry its own set of self-contained headers > consistent with its needs -- this has always been the case for all trees > apart from the sparse tree. For the tree which is going to be derived > from the sparse tree the build will check that the hypervisor headers > (xen/include/public) and the kernel headers > (linux-FOO.hg/include/xen/interface/) are in sync and error out in order > to prevent those two trees diverging. Hi Ian, when can we expect to see the new Linux tree created? I'm doing a lot of forward-porting of the PowerPC Linux patches, and so I will have a few generic Linux patches for the new tree. -- Hollis Blanchard IBM Linux Technology Center