All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: "Zulauf, John" <john.zulauf@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Timeline for migrating to newer Linux kernels?
Date: Sun, 31 Dec 2006 19:21:57 -0500	[thread overview]
Message-ID: <45985425.6010307@redhat.com> (raw)
In-Reply-To: <BD262A443AD428499D90AF8368C4528D1C2D9D@fmsmsx411.amr.corp.intel.com>

Zulauf, John wrote:
> What is the schedule/plan for moving the Xen linux kernel development to 
> the something far nearer the tip of the kernel.org tree?

This has been an ongoing issue for well over the last year.

XenSource has usually been less than useful when it comes
to tracking the upstream kernel.  I suspect they'll be
obsoleted by KVM and/or lhype at some point in the future,
because those will just be there in the upstream kernel
while Xen won't.

If XenSource has any intention of having Xen stay relevant
in the future, they'll want to seriously pursue an upstream
merge of their code.

At the moment Xen is still the leader when it comes to features
and performance (http://virt.kernelnewbies.org/TechComparison),
but who knows how long that will last?

-- 
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is.  Each group
calls the other unpatriotic.

  reply	other threads:[~2007-01-01  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 19:31 Timeline for migrating to newer Linux kernels? Zulauf, John
2007-01-01  0:21 ` Rik van Riel [this message]
2007-01-01 16:44   ` Keir Fraser
2007-01-02  9:49     ` Daniel P. Berrange
2007-01-02 10:07       ` Keir Fraser
2007-01-10  2:54       ` Jimi Xenidis
2007-01-02  1:20   ` Jeremy Fitzhardinge

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=45985425.6010307@redhat.com \
    --to=riel@redhat.com \
    --cc=john.zulauf@intel.com \
    --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.