WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Has 3.0.3 been released?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Has 3.0.3 been released?
From: Aron Griffis <aron@xxxxxx>
Date: Tue, 17 Oct 2006 18:26:40 -0400
Cc: Anthony Liguori <aliguori@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 17 Oct 2006 15:27:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C15B0FD8.2AFB%Keir.Fraser@xxxxxxxxxxxx>
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>
Mail-followup-to: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Anthony Liguori <aliguori@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
References: <20061017220124.GD27879@xxxxxxxxx> <C15B0FD8.2AFB%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
Keir Fraser wrote:  [Tue Oct 17 2006, 05:55:20PM EDT]
> > Will the tree structure change from the current sparse model to
> > a fully-populated kernel?  IMHO it wouldn't be too hard to use
> > something similar to
> > http://xenbits.xensource.com/ext/linux-2.6.tip-xen.hg plus a top-level
> > xen directory containing the hypervisor.  Alternatively, since Xen
> > isn't just Linux, maybe the hypervisor and kernels should be in
> > separate repositories?
> 
> Perhaps. We might at least separate the kernel bits from the
> hypervisor bits. We like working with a sparse tree as it's much
> quicker than cloning entire Linux repos.

I suppose xen/include/public synchronization also poses a challenge,
unless it's okay for the kernel to #include files outside of the
kernel tree.

Aron

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