From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: tim.post@netkinetics.net, xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>,
Ian Campbell <Ian.Campbell@xensource.com>
Subject: Re: 2.6.20.3 to be the next kernel?
Date: Mon, 04 Jun 2007 13:15:32 -0700 [thread overview]
Message-ID: <466472E4.9000505@goop.org> (raw)
In-Reply-To: <200706042058.37449.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
>> This time for sure. Well, its queued up in -mm and doesn't seem to have
>> caused any breakage there, and Linus has declared the patches "not too
>> bad".
>>
>
> Awesome. Is the plan to push some dom0 patches upstream eventually, or will
> that wait for a later date? Hopefully the major part of the operation is
> done with, though: distros can ship with paravirt domU compatibility by
> default.
>
I think the vendor position is that pv-ops xen is a nice start that just
makes things more complex for them in the short term, since it only
handles one quarter of the dom0-domU/32-64bit Xen parameter space. But
it's a start.
I'm starting on dom0 stuff now (with a minor detour via getting Xen to
boot bzImage kernels), mostly so I can get a feel for what the dom0
pv-ops patches will look like.
I'm also hoping that (ideally) x86-32 and -64 trees get merged in time
to make the 64-bit xen support trivial, but given that that's unlikely
anytime soon, I'm waiting for the 64-bit lguest/pv-ops people to get
x86-64 pv-ops in sync with 32-bit before starting on the Xen pieces. Of
course if that takes too long (ie, longer than dom0) I might have to get
more actively involved.
J
next prev parent reply other threads:[~2007-06-04 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:44 2.6.20.3 to be the next kernel? Tim Post
2007-06-04 18:01 ` Mark Williamson
2007-06-04 18:10 ` Daniel P. Berrange
2007-06-04 18:31 ` Mark Williamson
2007-06-04 18:13 ` Nate Carlson
2007-06-04 18:17 ` Daniel P. Berrange
2007-06-04 18:33 ` Mark Williamson
2007-06-04 19:04 ` Jeremy Fitzhardinge
2007-06-04 19:58 ` Mark Williamson
2007-06-04 20:00 ` Daniel P. Berrange
2007-06-04 20:16 ` Jeremy Fitzhardinge
2007-06-04 20:15 ` Jeremy Fitzhardinge [this message]
2007-06-05 2:24 ` Mark Williamson
2007-06-05 4:50 ` Jeremy Fitzhardinge
2007-06-05 4:57 ` Jeremy Fitzhardinge
2007-06-05 15:57 ` Mark Williamson
2007-06-05 3:49 ` Tim Post
2007-06-05 4:53 ` 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=466472E4.9000505@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@xensource.com \
--cc=berrange@redhat.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=tim.post@netkinetics.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.