* Question about xen/stable branch in kernel pv_ops
@ 2010-02-25 8:59 Fantu
2010-02-25 10:09 ` Pasi Kärkkäinen
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Fantu @ 2010-02-25 8:59 UTC (permalink / raw)
To: xen-devel
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?
Thanks advance for any reply
--
View this message in context: http://old.nabble.com/Question-about-xen-stable-branch-in-kernel-pv_ops-tp27714378p27714378.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Question about xen/stable branch in kernel pv_ops
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 19:05 ` Jeremy Fitzhardinge
2 siblings, 0 replies; 9+ messages in thread
From: Pasi Kärkkäinen @ 2010-02-25 10:09 UTC (permalink / raw)
To: Fantu; +Cc: xen-devel
On Thu, Feb 25, 2010 at 12:59:30AM -0800, 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 don't know what's the status of xen/stable, I haven't tried it yet.
Maybe Jeremy can comment on that..
You can also clone/checkout and build it separately, no need to build it as
part of Xen hypervisor.
> 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?
>
I assume you're talking about XenParavirtOps wiki page.
I added CONFIG_XEN_PCIDEV_FRONTEND=y there yesterday based on Konrad's request,
but it seems I don't have it in my example .config files.
-- Pasi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Question about xen/stable branch in kernel pv_ops
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 19:05 ` Jeremy Fitzhardinge
2 siblings, 1 reply; 9+ messages in thread
From: M A Young @ 2010-02-25 10:56 UTC (permalink / raw)
To: Fantu; +Cc: xen-devel
On Thu, 25 Feb 2010, 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 seems to be xen/next plus merges up to v2.6.32.9 . I did a
build based on it yesterday, and it seems to work the same as xen/next
did.
Michael Young
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Question about xen/stable branch in kernel pv_ops
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
0 siblings, 1 reply; 9+ messages in thread
From: Pasi Kärkkäinen @ 2010-02-25 11:55 UTC (permalink / raw)
To: M A Young; +Cc: xen-devel, Fantu
On Thu, Feb 25, 2010 at 10:56:14AM +0000, M A Young wrote:
> On Thu, 25 Feb 2010, 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 seems to be xen/next plus merges up to v2.6.32.9 . I did a
> build based on it yesterday, and it seems to work the same as xen/next
> did.
>
Yeah, xen/stable is going to be the 'long term maintained' branch,
based on the long term maintained upstream 2.6.32.
See:
http://lists.xensource.com/archives/html/xen-devel/2009-12/msg01127.html
-- Pasi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Question about xen/stable branch in kernel pv_ops
2010-02-25 11:55 ` Pasi Kärkkäinen
@ 2010-02-25 16:05 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-02-25 16:05 UTC (permalink / raw)
To: Pasi Kärkkäinen; +Cc: xen-devel, Fantu, M A Young
On Thu, Feb 25, 2010 at 01:55:39PM +0200, Pasi Kärkkäinen wrote:
> On Thu, Feb 25, 2010 at 10:56:14AM +0000, M A Young wrote:
> > On Thu, 25 Feb 2010, 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?
That is my fault. I was hoping to have the PCI frontend branch ready by
the time Pasi would have added that in (and ask Jeremy to merge it in),
but I am still trying to narrow down the list of patches.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Question about xen/stable branch in kernel pv_ops
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 19:05 ` Jeremy Fitzhardinge
2010-02-26 8:30 ` Fabio Fantoni
2 siblings, 1 reply; 9+ messages in thread
From: Jeremy Fitzhardinge @ 2010-02-25 19:05 UTC (permalink / raw)
To: Fantu; +Cc: xen-devel
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
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Question about xen/stable branch in kernel pv_ops
2010-02-25 19:05 ` Jeremy Fitzhardinge
@ 2010-02-26 8:30 ` Fabio Fantoni
2010-02-26 8:42 ` Pasi Kärkkäinen
0 siblings, 1 reply; 9+ messages in thread
From: Fabio Fantoni @ 2010-02-26 8:30 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1444 bytes --]
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 - 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.
[-- Attachment #1.2: Type: text/html, Size: 2009 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Question about xen/stable branch in kernel pv_ops
2010-02-26 8:30 ` Fabio Fantoni
@ 2010-02-26 8:42 ` Pasi Kärkkäinen
2010-03-01 7:28 ` Fantu
0 siblings, 1 reply; 9+ messages in thread
From: Pasi Kärkkäinen @ 2010-02-26 8:42 UTC (permalink / raw)
To: Fabio Fantoni; +Cc: Jeremy Fitzhardinge, xen-devel
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Question about xen/stable branch in kernel pv_ops
2010-02-26 8:42 ` Pasi Kärkkäinen
@ 2010-03-01 7:28 ` Fantu
0 siblings, 0 replies; 9+ messages in thread
From: Fantu @ 2010-03-01 7:28 UTC (permalink / raw)
To: xen-devel
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.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2010-03-01 7:28 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).