All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: [FW: FYI: The plan for Xen kernels in Fedora 9]
Date: Mon, 10 Dec 2007 21:55:00 +0000	[thread overview]
Message-ID: <20071210215500.GC21814@redhat.com> (raw)
In-Reply-To: <200712102138.50396.mark.williamson@cl.cam.ac.uk>

On Mon, Dec 10, 2007 at 09:38:49PM +0000, Mark Williamson wrote:
> > In the spirit of improving communication of Fedora Xen plans to the world,
> > below is a mail I recently circulated in the Fedora community about the
> > direction for Xen-ified kernels from Fedora 9 and onwards.
> >
> > The short story, is that we intend to ship hypervisor & userspace based on
> > Xen 3.2.0 tree, and a kernel based on latest LKML pv_ops tree and patches
> > ontop of that to support Dom0 and x86_64. With some short term pain and
> > instability, we hope to get significant long term benefits for support of
> > Xen Linux kernels.
> 
> Sounds like the best possible and longterm-sustainable plan and good for 
> everybody involved.
> 
> Question: do the dom0-compatibility patches have any chance of getting into 
> kernel.org?  Or would they continue to live as a patchset?

That's a huge open ended question & you can't take anything for granted when
its comes to LKML review / feedback. I'd like to think they have a reasonable
chance, but its all depends how intrusive the changes become. Even if they
don't get accepted upstream, at least they'll be reconciled against current
accepted  DomU patches. So at worst, we have an incremental improvement in
the maintainability, at best a dramatic improvement.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

      parent reply	other threads:[~2007-12-10 21:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 15:20 [FW: FYI: The plan for Xen kernels in Fedora 9] Daniel P. Berrange
2007-12-10 15:32 ` Keir Fraser
2007-12-10 17:06 ` Stephen C. Tweedie
2007-12-10 17:38   ` Stephen C. Tweedie
2007-12-11  0:31     ` Chuck Short
2007-12-11 17:41       ` Stephen C. Tweedie
2007-12-11  0:36   ` Jeremy Fitzhardinge
2007-12-11  1:30     ` Tian, Kevin
2007-12-11  1:36       ` Jeremy Fitzhardinge
2007-12-11  1:46         ` Tian, Kevin
2007-12-11 12:08     ` Stephen C. Tweedie
2007-12-11 16:57       ` Jeremy Fitzhardinge
2007-12-11 17:39         ` Stephen C. Tweedie
2007-12-10 17:47 ` Stephen C. Tweedie
2007-12-10 19:12 ` Jeremy Fitzhardinge
2007-12-10 21:38 ` Mark Williamson
2007-12-10 21:48   ` Jeremy Fitzhardinge
2007-12-11 17:32     ` Stephen C. Tweedie
2007-12-11 19:24       ` Jeremy Fitzhardinge
2007-12-10 21:55   ` Daniel P. Berrange [this message]

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=20071210215500.GC21814@redhat.com \
    --to=berrange@redhat.com \
    --cc=jeremy@goop.org \
    --cc=mark.williamson@cl.cam.ac.uk \
    --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.