From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: which branch is recommanded to use for pvops dom0?
Date: Mon, 24 Jan 2011 17:45:14 -0800 [thread overview]
Message-ID: <4D3E2B2A.7020708@goop.org> (raw)
In-Reply-To: <749B9D3DBF0F054390025D9EAFF47F2231C1349A@shsmsx501.ccr.corp.intel.com>
On 01/24/2011 05:33 PM, Zhang, Yang Z wrote:
> Hi jeremy
> Now we use xen/stable-2.6.32.x for testing. But I found the xen/stable-2.6.33.x is ready? Should we move to it?
>
There is no xen/stable-2.6.33; there might have been at one point, but
it was never more than a placeholder.
What kind of work are you doing?
Mainline Linux contains a lot of dom0 support now, but not quite enough
to usefully run a domain. We're in the middle of preparing a 2.6.38-rc
based branch which will be more complete.
xen/stable-2.6.32.x is still the most feature-complete branch, but it is
more or less in a maintenance state, and will probably only get bugfix
updates.
J
next prev parent reply other threads:[~2011-01-25 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 1:33 which branch is recommanded to use for pvops dom0? Zhang, Yang Z
2011-01-25 1:45 ` Jeremy Fitzhardinge [this message]
2011-01-25 1:59 ` which branch is recommended " Zhang, Yang Z
2011-01-25 13:25 ` Re: which branch is recommanded " Gianni Tedesco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D3E2B2A.7020708@goop.org \
--to=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.