From: Rusty Russell <rusty@rustcorp.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Paravirt-ops VMI / Xen / lrustyvisor merge status
Date: Fri, 09 Feb 2007 16:54:34 +1100 [thread overview]
Message-ID: <1171000474.2718.8.camel@localhost.localdomain> (raw)
In-Reply-To: <45CC0672.7090201@vmware.com>
On Thu, 2007-02-08 at 21:28 -0800, Zachary Amsden wrote:
> So, as 2.6.21-rc1 is approaching, what is the upstream merge status for
> the paravirt-ops backends? I believe VMI is in Andi's tree, plus or
> minus some bugfixes that are still being whittled in, but Andi, do you
> think the VMI code is in good shape for merging?
>
> It would be nice for everyone to clarify their upstream plans - is the
> goal still to get Xen and lguest merged for the next kernel release?
>
> Rusty, you mentioned you had a patchset to push, when do you expect to
> have it ready?
I'm just doing the final file moving now (everything in
arch/i386/lguest), expect to send out something within 48 hours (I need
to sync up to latest git tree, too).
> One of which is separating the paravirt-ops into GPL
> and non-GPL exports, which we need consensus on where the line is, but
> can't really achieve it until everyone is happy with the finalized set
> of paravirt-ops. Any patch that tries to do this now would just cause
> rejects later and slow all of our merges.
Yes, I have a patch, but it breaks kvm. I'm waiting until things settle
before fixing it.
Cheers,
Rusty.
next prev parent reply other threads:[~2007-02-09 5:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:28 Paravirt-ops VMI / Xen / lrustyvisor merge status Zachary Amsden
2007-02-09 5:54 ` Rusty Russell [this message]
2007-02-09 6:12 ` Zachary Amsden
2007-02-09 6:24 ` Jeremy Fitzhardinge
2007-02-09 6:58 ` Zachary Amsden
2007-02-09 6:44 ` Rusty Russell
2007-02-09 6:57 ` Jeremy Fitzhardinge
2007-02-09 6:59 ` Zachary Amsden
2007-02-09 7:06 ` Jeremy Fitzhardinge
2007-02-09 7:20 ` Rusty Russell
2007-02-09 7:35 ` Andi Kleen
2007-02-09 8:46 ` Rusty Russell
2007-02-09 6:10 ` Jeremy Fitzhardinge
2007-02-09 7:21 ` Andi Kleen
2007-02-09 7:35 ` Zachary Amsden
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=1171000474.2718.8.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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.