From: Greg KH <greg@kroah.com>
To: Alok Kataria <akataria@vmware.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.osdl.org
Subject: Re: Paravirtualization on VMware's Platform [VMI].
Date: Sat, 19 Sep 2009 15:44:30 -0700 [thread overview]
Message-ID: <20090919224430.GB9567@kroah.com> (raw)
In-Reply-To: <1253233028.19731.63.camel@ank32.eng.vmware.com>
On Thu, Sep 17, 2009 at 05:17:08PM -0700, Alok Kataria wrote:
> Given this new development, I wanted to discuss how should we go about
> retiring the VMI code from mainline Linux, i.e. the vmi_32.c and
> vmiclock_32.c bits.
>
> One of the options that I am contemplating is to drop the code from the
> tip tree in this release cycle, and given that this should be a low risk
> change we can remove it from Linus's tree later in the merge cycle.
That sounds good to me, how intrusive are the patches to do this? Is it
going to be tricky to get everything merged properly in -tip for it?
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-19 22:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 0:17 Paravirtualization on VMware's Platform [VMI] Alok Kataria
2009-09-18 0:34 ` Chris Wright
2009-09-18 0:53 ` Jeremy Fitzhardinge
2009-09-18 0:58 ` Chris Wright
2009-09-18 1:43 ` Alok Kataria
2009-09-19 7:43 ` Avi Kivity
2009-09-19 22:44 ` Greg KH [this message]
2009-09-20 1:04 ` Jeremy Fitzhardinge
2009-09-20 3:56 ` Alok Kataria
2009-09-20 3:59 ` Alok Kataria
2009-09-20 7:42 ` Ingo Molnar
2009-09-20 7:52 ` Arjan van de Ven
2009-09-20 9:00 ` Avi Kivity
2009-09-20 15:49 ` Jeremy Fitzhardinge
2009-09-20 19:00 ` Avi Kivity
2009-09-22 8:09 ` Ingo Molnar
2009-09-22 16:52 ` Jeremy Fitzhardinge
2009-09-22 18:02 ` Ingo Molnar
2009-09-22 18:16 ` Jeremy Fitzhardinge
2009-09-22 19:04 ` Ingo Molnar
2009-09-22 19:30 ` Jeremy Fitzhardinge
2009-09-22 7:22 ` Rusty Russell
2009-09-22 16:53 ` Jeremy Fitzhardinge
2009-09-22 19:30 ` Alok Kataria
2009-09-22 19:47 ` Jeremy Fitzhardinge
2009-09-22 21:27 ` H. Peter Anvin
2009-09-22 21:54 ` Alok Kataria
2009-09-22 22:58 ` H. Peter Anvin
2009-09-23 7:29 ` Gerd Hoffmann
2009-09-29 0:45 ` Alok Kataria
2009-09-29 2:25 ` H. Peter Anvin
2009-09-29 3:00 ` Alok Kataria
2009-09-29 9:01 ` Chris Wright
2009-09-29 17:25 ` Alok Kataria
2009-09-29 17:27 ` H. Peter Anvin
2009-09-29 17:36 ` Alok Kataria
2009-09-29 18:21 ` Chris Wright
2009-09-29 8:08 ` Arjan van de Ven
2009-09-29 16:49 ` Alok Kataria
2009-09-29 16:51 ` H. Peter Anvin
2009-09-29 17:55 ` Learning question regarding virtio and partvirt_ops Hank Janssen
2009-09-29 19:02 ` Brian Jackson
2009-10-02 3:00 ` Paravirtualization on VMware's Platform [VMI] Eric W. Biederman
2009-10-02 4:45 ` Alok Kataria
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=20090919224430.GB9567@kroah.com \
--to=greg@kroah.com \
--cc=akataria@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.osdl.org \
--cc=x86@kernel.org \
/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).