[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Question about xen/stable branch in kernel pv_ops
On Fri, Feb 26, 2010 at 09:30:15AM +0100, Fabio Fantoni wrote: > Il 25/02/2010 20:05, Jeremy Fitzhardinge ha scritto: > > 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 > > > > Nessun virus nel messaggio in arrivo. > Controllato da AVG - [1]www.avg.com > Versione: 9.0.733 / Database dei virus: 271.1.1/2709 - Data di rilascio: > 02/25/10 08:34:00 > > > > I have try to change xen/master in xen/stable or xen/next but give error: > error: pathspec 'xen/stable' did not match any file(s) known to git. > error: pathspec 'xen/next' did not match any file(s) known to git. > git pull git reset --hard git checkout -b xen/stable origin/xen/stable git pull and verify the changelog with "git log" and compare to output from: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/stable -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |