From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Fantu <fantonifabio@tiscali.it>
Cc: xen-devel@lists.xensource.com
Subject: Re: Question about xen/stable branch in kernel pv_ops
Date: Thu, 25 Feb 2010 11:05:38 -0800 [thread overview]
Message-ID: <4B86CA02.9020404@goop.org> (raw)
In-Reply-To: <27714378.post@talk.nabble.com>
On 02/25/2010 12:59 AM, Fantu wrote:
> I see new branch (xen/stable) in pv_ops based on 2.6.32.9, is good? for test
> it there only to change xen/master in xen/stable in
> buildconfig/mk.linux-2.6-pvops right?
> I also see update in this page, for use config example for xen/stable i must
> use "64bit x86_64 (xen/next 2.6.32)"?
> Why is add CONFIG_XEN_PCIDEV_FRONTEND=y in page but there isn't in example
> config?
>
xen/stable is still a work in progress, but it should be suitable for
general use. It is based on xen/next (which is 2.6.32 based), but it
also has the 2.6.32.x stable kernels merged into it.
At the moment it is missing a few features compared to xen/master; in
particular it is missing PCI passthrough and ACPI power management.
This will become a long-term supported Xen kernel (as 2.6.32 is going to
be a long-term supported Linux release). There will also be a
development tree which tracks ongoing Linux development.
J
next prev parent reply other threads:[~2010-02-25 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 8:59 Question about xen/stable branch in kernel pv_ops Fantu
2010-02-25 10:09 ` Pasi Kärkkäinen
2010-02-25 10:56 ` M A Young
2010-02-25 11:55 ` Pasi Kärkkäinen
2010-02-25 16:05 ` Konrad Rzeszutek Wilk
2010-02-25 19:05 ` Jeremy Fitzhardinge [this message]
2010-02-26 8:30 ` Fabio Fantoni
2010-02-26 8:42 ` Pasi Kärkkäinen
2010-03-01 7:28 ` Fantu
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=4B86CA02.9020404@goop.org \
--to=jeremy@goop.org \
--cc=fantonifabio@tiscali.it \
--cc=xen-devel@lists.xensource.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.