All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Tramnitz <chris.ace@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: Future of xenbits Linux trees
Date: Fri, 05 Jun 2009 15:26:30 +0200	[thread overview]
Message-ID: <h0b67q$lsg$1@ger.gmane.org> (raw)
In-Reply-To: <C64DAAA6.788E%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> What do people think of this as a plan?

I'd opt for an approach based on the available 2.6.29 tree from Andrew 
but delayed until 2.6.30 is out.

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.
On the other hand it might make sense to use the same kernel version 
that RHEL6 will be using to take advantage of their (driver-) 
backporting efforts (not sure how heavily that has been utilized in 
2.6.18). Any insider infos from the RH guys here on the list what kernel 
that might be? ;-)



As a side-note, there is known issue with Andrew's tree not compiling on 
x86_32 with a recent gcc. If I remember correctly that was due to 
optimizations, further details here: 
http://forums.gentoo.org/viewtopic-p-5667545.html#5667545


Best regards,
    Christian

  parent reply	other threads:[~2009-06-05 13:26 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 [this message]
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
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='h0b67q$lsg$1@ger.gmane.org' \
    --to=chris.ace@gmx.net \
    --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.