From: Gerd Hoffmann <kraxel@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Christian Tramnitz <chris.ace@gmx.net>
Subject: Re: Re: Future of xenbits Linux trees
Date: Fri, 05 Jun 2009 18:41:05 +0200 [thread overview]
Message-ID: <4A294AA1.5060003@redhat.com> (raw)
In-Reply-To: <C64EDDF5.7916%keir.fraser@eu.citrix.com>
On 06/05/09 15:36, Keir Fraser wrote:
> On 05/06/2009 14:26, "Christian Tramnitz"<chris.ace@gmx.net> wrote:
>
>> Simple reason, there are so many fundamental changes in/before 2.6.29
>> i.e. ext4 and in terms of video support (KMS, GEM) that anything before
>> 2.6.29 (such as the 2.6.27 XCI tree) will be a waste of efforts if that
>> will be the next tree that should have long-term (until pvops merges
>> upstream, haha) support.
>
> We don't need to wait for pv_ops to be merged. We just need it to have
> near-enough feature parity. Actually now it supports HVM guests I'm tempted
> to just move over to it.
Go ahead! It is really time to stop forward-porting stuff. The time is
much better spent in adding the missing features to pv_ops/dom0. Also
just after the 3.4 release is the perfect moment for that move, 3.5
should be able to ship with a pv_ops based kernel then.
cheers,
Gerd
next prev parent reply other threads:[~2009-06-05 16:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 15:45 Future of xenbits Linux trees Keir Fraser
2009-06-04 16:09 ` Jean Guyader
2009-06-04 16:16 ` Tim Post
2009-06-04 18:08 ` Espen Skoglund
2009-06-04 18:17 ` Keir Fraser
2009-06-04 18:21 ` Jean Guyader
2009-06-05 7:32 ` Andrew Lyon
2009-06-05 7:46 ` Pasi Kärkkäinen
2009-06-05 7:52 ` Keir Fraser
2009-06-05 7:58 ` Jean Guyader
2009-06-05 8:30 ` Pasi Kärkkäinen
2009-06-05 18:51 ` Andy Burns
2009-06-07 17:09 ` Pasi Kärkkäinen
2009-06-07 18:36 ` M A Young
2009-06-07 18:52 ` Andy Burns
2009-06-05 13:26 ` Christian Tramnitz
2009-06-05 13:36 ` Keir Fraser
2009-06-05 14:05 ` Dulloor
2009-06-05 14:37 ` Ian Pratt
2009-06-05 17:13 ` Gerd Hoffmann
2009-06-05 14:05 ` Christian Tramnitz
2009-06-05 16:41 ` Gerd Hoffmann [this message]
2009-06-05 17:58 ` AW: Re: " Carsten Schiers
2009-06-05 18:49 ` Keir Fraser
2009-06-05 21:02 ` AW: " Carsten Schiers
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=4A294AA1.5060003@redhat.com \
--to=kraxel@redhat.com \
--cc=chris.ace@gmx.net \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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.