Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] new repo layout?

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] new repo layout?
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Thu, 31 May 2007 11:02:05 -0500
Cc: Aron Griffis <aron@xxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 31 May 2007 09:00:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1180598644.29571.57.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
Organization: IBM Linux Technology Center
References: <20070530214638.GA21589@xxxxxxxxx> <1180598644.29571.57.camel@xxxxxxxxxxxxxxxxxxxxx>
Reply-to: Hollis Blanchard <hollisb@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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


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

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