public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok Kataria <akataria@vmware.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>, 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" <virtualization@lists.osdl.org>,
	Greg KH <greg@kroah.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Paravirtualization on VMware's Platform [VMI].
Date: Tue, 29 Sep 2009 09:49:49 -0700	[thread overview]
Message-ID: <1254242989.7803.11.camel@ank32.eng.vmware.com> (raw)
In-Reply-To: <20090929100831.18ece319@infradead.org>


On Tue, 2009-09-29 at 01:08 -0700, Arjan van de Ven wrote:
> > For now I have just added some text in the feature-removal file and
> > disabled VMI by default in the Kconfig, the reason that needs to be
> > done is because "Live Migration" of a VMI enabled VM to future
> > products which don't support VMI will not work, so its important that
> > newer distros keep this disabled, if they want seamless migration
> > that is.
> 
> btw the "default" in KConfig tends to be totally ignored by distro
> kernel maintainers... please don't assume that just because some default
> is set in KConfig it has ANY impact on what shows up in distributions.

So, are you saying that we should be doing something else along with
toggling it off in the Kconfig ? 
We have already informed most of the distro folks about this deprecation
so I think we should be okay there, but if there is something else that
should be done, do let me know.

Thanks,
Alok




  reply	other threads:[~2009-09-29 16:49 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
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-10-08 20:24                 ` [tip:x86/urgent] x86, vmi: Mark VMI deprecated and schedule it for remval tip-bot for Alok Kataria
2009-10-08 20:34                 ` [tip:x86/urgent] x86, vmi: Mark VMI deprecated and schedule it for removal tip-bot for Alok Kataria
2009-09-29  8:08             ` Paravirtualization on VMware's Platform [VMI] Arjan van de Ven
2009-09-29 16:49               ` Alok Kataria [this message]
2009-09-29 16:51                 ` H. Peter Anvin
2009-10-02  3:00                 ` 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=1254242989.7803.11.camel@ank32.eng.vmware.com \
    --to=akataria@vmware.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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