xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Josip Rodin <joy@entuzijast.net>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xen.git plans / 2.6.32 long-term stable kernel
Date: Wed, 27 Jan 2010 12:32:00 +0100	[thread overview]
Message-ID: <20100127113200.GA11864@orion.carnet.hr> (raw)
In-Reply-To: <529a12f41001251237q5acb5c43nec34bf5b9bad5188@mail.gmail.com>

On Mon, Jan 25, 2010 at 10:37:41PM +0200, Sassy Natan wrote:
> I wonder when the Linux group will decide to include xen dom0 support in
> the mainline?

Based on Jeremy's November presentation, that's not actually that important,
because the dom0 paravirt_ops support doesn't have a pressing need to
qualify for mainline Linux inclusion standards, while there is a practical
matter of it needing to become a qualified replacement for the old 2.6.18
kernel Xen patch. That patch has continued to be forward-ported to newer
versions and shipped with distribution kernels, which is what most users
use, but that process is becoming untenable as the kernel versions continue
to diverge.

-- 
     2. That which causes joy or happiness.

  reply	other threads:[~2010-01-27 11:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 20:59 xen.git plans Jeremy Fitzhardinge
2010-01-20 10:18 ` xen.git plans / 2.6.32 long-term stable kernel Pasi Kärkkäinen
2010-01-20 18:40   ` Jeremy Fitzhardinge
2010-01-20 18:55     ` Pasi Kärkkäinen
2010-01-25 20:37       ` Sassy Natan
2010-01-27 11:32         ` Josip Rodin [this message]
2010-01-27 11:41           ` Pasi Kärkkäinen
2010-01-25 13:38     ` Josip Rodin
2010-01-25 20:48       ` Sassy Natan

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=20100127113200.GA11864@orion.carnet.hr \
    --to=joy@entuzijast.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 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).