From: Christian Tramnitz <chris.ace@gmx.net>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Future of xenbits Linux trees
Date: Fri, 05 Jun 2009 16:05:39 +0200 [thread overview]
Message-ID: <4A292633.1070802@gmx.net> (raw)
In-Reply-To: <C64EDDF5.7916%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> 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. It would probably make sense to keep Jeremy as
> gatekeeper for that tree, which will take some of his time. Otoh I'm not
> sure spending 100% of your time banging your head against lkml is much fun.
> :-)
>
> Probably the major thing it's missing for a simple complete changeover is
> ia64/Xen support. We could continue to point the ia64 build target at
> linux-2.6.18-xen though.
Afaik pvops (even /next) also has no pci_backend support yet and even
the pci_frontend support is mainly untested.
Both (front/back) work great with Andrew's 2.6.29 tree, although I
haven't seen ANY reports of IA64 running off it.
I would also consider pvops to be a moving target (you know... lkml fun)
so I wouldn't really base anything on it until the structure has been
approved. Maintaining two different pvops lines (one with all changes as
requested by mainline maintainers and one "stable") might to much of a
burden if we already have a working 2.6.29 with (hopefully) not much
work to do other than extensive testing before announcing it as 2.6.18
successor.
Best regards,
Christian
next prev parent reply other threads:[~2009-06-05 14:05 UTC|newest]
Thread overview: 39+ 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 [this message]
2009-06-05 16:41 ` Gerd Hoffmann
2009-06-05 17:58 ` AW: " Carsten Schiers
2009-06-05 18:49 ` Keir Fraser
2009-06-05 21:02 ` AW: " Carsten Schiers
-- strict thread matches above, loose matches on Subject: below --
2009-06-04 18:01 Boris Derzhavets
2009-06-04 18:46 ` Jean Guyader
2009-06-04 19:08 ` Keir Fraser
2009-06-04 19:13 ` Jean Guyader
2009-06-05 7:37 Boris Derzhavets
2009-06-05 7:53 Boris Derzhavets
2009-06-05 23:05 ` Genki Kuroda
2009-06-06 2:17 ` Kamala Narasimhan
2009-06-06 2:48 ` Genki Kuroda
2009-06-06 2:53 ` Kamala Narasimhan
2009-06-06 5:26 ` Genki Kuroda
2009-06-06 9:54 ` Jean Guyader
2009-06-05 10:44 Boris Derzhavets
2009-06-06 20:11 Boris Derzhavets
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=4A292633.1070802@gmx.net \
--to=chris.ace@gmx.net \
--cc=jeremy@goop.org \
--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.