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/
Home Products Support Community News


[Xen-devel] pvops dom0 work roadmap

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] pvops dom0 work roadmap
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 18 Aug 2009 11:43:38 -0700
Delivery-date: Tue, 18 Aug 2009 11:44:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3
Hi all,

I know I've been a bit quiet lately;  I've been working through a number
of relatively small but time-consuming bugs while trying to stabilize

The plan is:

    * make sure rebase/master is fairly functional and somewhat stable
    * rename rebase/* to xen/*
    * use it as the baseline dom0 and domU kernel in xen-unstable

rebase/mster is currently up to 2.6.31-rc6, and I intend to track
mainline fairly closely (probably no more closely than the -rc level). 
It also has some new features:

    * better acpi power management (ported from 2.6.18)
    * MCE (also from 2.6.18)
    * microcode updater (I forget whether that's in xen-tip/master)

rebase/master is mostly working for me now, but I would be interested in
getting some more testing (both success and bug reports welcomed).  Once
it seems to work, I'll do the rename and we'll work from there.

What does this mean for you?

    * If you're itching to test something, test rebase/master
    * If you're doing some new development, base it on rebase/master (or
      if you don't have any strong dependencies on other Xen pieces,
      base it on mainline)
          o also, tell me if you're working on something, even if it
            isn't ready yet, so I know who's doing what

It would also useful to do regression testing on plain, unpatched,
mainline, to make sure that any real bugfixes get merged promptly.


Xen-devel mailing list