All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Question about xen/stable branch in kernel pv_ops
Date: Sun, 28 Feb 2010 23:28:45 -0800 (PST)	[thread overview]
Message-ID: <27740714.post@talk.nabble.com> (raw)
In-Reply-To: <20100226084213.GJ2761@reaktio.net>


Now with config example in wiki page do very big modules and initrd, is
possible do same config without only not necessary for do more small?

Pasi Kärkkäinen wrote:
> 
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Question-about-xen-stable-branch-in-kernel-pv_ops-tp27714378p27740714.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

      reply	other threads:[~2010-03-01  7:28 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
2010-02-26  8:30   ` Fabio Fantoni
2010-02-26  8:42     ` Pasi Kärkkäinen
2010-03-01  7:28       ` Fantu [this message]

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=27740714.post@talk.nabble.com \
    --to=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.