Re: [Xen-devel] Future of xenbits Linux trees

[Espen Skoglund <espen.skoglund@xxxxxxxxxxxxx>]

Sounds reasonable.  The 2.6.18 tree is getting a bit dated now.

One question: How complete is the XCI tree with respect to the various
Xen related features having been added to the 2.6.18 tree over time?
Is it all in there?

        eSk



[Keir Fraser]
> Folks,
> With 3.4 out the door it is time to revisit the state of our Linux
> repositories. Currently we have a number of trees in various states of
> maintenance:
>  - linux-2.6.18-xen.hg: the 'original' tree. Still maintained, used and
> tested but increasingly long in the tooth.
>  - ext/linux-2.6.27-xen.hg: a snapshot of opensuse's kernel port. This
> clones tree is not maintained or tested.
>  - XCI/linux-2.6.27.git: a forward port of the Xen patches to 2.6.27.
> Maintained as part of XCI project.
>  - Jeremy's pv_ops patches against kernel.org: maintained, (somewhat)
> tested, but incomplete.

> It is probably time to kill the 2.6.18 tree, or at least stop active
> development within it. It is increasingly a kludged collection of
> backports of more recent kernel patches, and is also missing a lot
> of drivers for more modern hardware.

> Our proposal is to move XCI's linux-2.6.27 tree out of the XCI
> subproject and make it the main user tree. Development and automated
> testing would occur on that tree and of course on Jeremy's pv_ops
> patchset (which we want to completely move onto at some point in the
> future).

> What do people think of this as a plan?

>  -- Keir



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


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