public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Alok Kataria <akataria@vmware.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	chrisw@sous-sol.org, akataria@vmware.com, tglx@linutronix.de,
	mingo@elte.hu
Subject: [tip:x86/urgent] x86, vmi: Mark VMI deprecated and schedule it for removal
Date: Thu, 8 Oct 2009 20:34:07 GMT	[thread overview]
Message-ID: <tip-d0153ca35d344d9b640dc305031b0703ba3f30f0@git.kernel.org> (raw)
In-Reply-To: <1254193238.13456.48.camel@ank32.eng.vmware.com>

Commit-ID:  d0153ca35d344d9b640dc305031b0703ba3f30f0
Gitweb:     http://git.kernel.org/tip/d0153ca35d344d9b640dc305031b0703ba3f30f0
Author:     Alok Kataria <akataria@vmware.com>
AuthorDate: Tue, 29 Sep 2009 10:25:24 -0700
Committer:  Ingo Molnar <mingo@elte.hu>
CommitDate: Thu, 8 Oct 2009 22:27:55 +0200

x86, vmi: Mark VMI deprecated and schedule it for removal

Add text in feature-removal.txt indicating that VMI will be removed in
the 2.6.37 timeframe.

Signed-off-by: Alok N Kataria <akataria@vmware.com>
Acked-by: Chris Wright <chrisw@sous-sol.org>
LKML-Reference: <1254193238.13456.48.camel@ank32.eng.vmware.com>
[ removed a bogus Kconfig change, marked (DEPRECATED) in Kconfig ]
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 Documentation/feature-removal-schedule.txt |   30 ++++++++++++++++++++++++++++
 arch/x86/Kconfig                           |   11 +++++++++-
 arch/x86/kernel/vmi_32.c                   |    2 +-
 3 files changed, 41 insertions(+), 2 deletions(-)

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 89a47b5..04e6c81 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -451,3 +451,33 @@ Why:	OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR
 	will also allow making ALSA OSS emulation independent of
 	sound_core.  The dependency will be broken then too.
 Who:	Tejun Heo <tj@kernel.org>
+
+----------------------------
+
+What:	Support for VMware's guest paravirtuliazation technique [VMI] will be
+	dropped.
+When:	2.6.37 or earlier.
+Why:	With the recent innovations in CPU hardware acceleration technologies
+	from Intel and AMD, VMware ran a few experiments to compare these
+	techniques to guest paravirtualization technique on VMware's platform.
+	These hardware assisted virtualization techniques have outperformed the
+	performance benefits provided by VMI in most of the workloads. VMware
+	expects that these hardware features will be ubiquitous in a couple of
+	years, as a result, VMware has started a phased retirement of this
+	feature from the hypervisor. We will be removing this feature from the
+	Kernel too. Right now we are targeting 2.6.37 but can retire earlier if
+	technical reasons (read opportunity to remove major chunk of pvops)
+	arise.
+
+	Please note that VMI has always been an optimization and non-VMI kernels
+	still work fine on VMware's platform.
+	Latest versions of VMware's product which support VMI are,
+	Workstation 7.0 and VSphere 4.0 on ESX side, future maintainence
+	releases for these products will continue supporting VMI.
+
+	For more details about VMI retirement take a look at this,
+	http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html
+
+Who:	Alok N Kataria <akataria@vmware.com>
+
+----------------------------
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index c876bac..07e0114 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -491,7 +491,7 @@ if PARAVIRT_GUEST
 source "arch/x86/xen/Kconfig"
 
 config VMI
-	bool "VMI Guest support"
+	bool "VMI Guest support (DEPRECATED)"
 	select PARAVIRT
 	depends on X86_32
 	---help---
@@ -500,6 +500,15 @@ config VMI
 	  at the moment), by linking the kernel to a GPL-ed ROM module
 	  provided by the hypervisor.
 
+	  As of September 2009, VMware has started a phased retirement
+	  of this feature from VMware's products. Please see
+	  feature-removal-schedule.txt for details.  If you are
+	  planning to enable this option, please note that you cannot
+	  live migrate a VMI enabled VM to a future VMware product,
+	  which doesn't support VMI. So if you expect your kernel to
+	  seamlessly migrate to newer VMware products, keep this
+	  disabled.
+
 config KVM_CLOCK
 	bool "KVM paravirtualized clock"
 	select PARAVIRT
diff --git a/arch/x86/kernel/vmi_32.c b/arch/x86/kernel/vmi_32.c
index 31e6f6c..d430e4c 100644
--- a/arch/x86/kernel/vmi_32.c
+++ b/arch/x86/kernel/vmi_32.c
@@ -648,7 +648,7 @@ static inline int __init activate_vmi(void)
 
 	pv_info.paravirt_enabled = 1;
 	pv_info.kernel_rpl = kernel_cs & SEGMENT_RPL_MASK;
-	pv_info.name = "vmi";
+	pv_info.name = "vmi [deprecated]";
 
 	pv_init_ops.patch = vmi_patch;
 

  parent reply	other threads:[~2009-10-08 20:35 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-bot for Alok Kataria [this message]
2009-09-29  8:08             ` Paravirtualization on VMware's Platform [VMI] Arjan van de Ven
2009-09-29 16:49               ` Alok Kataria
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=tip-d0153ca35d344d9b640dc305031b0703ba3f30f0@git.kernel.org \
    --to=akataria@vmware.com \
    --cc=chrisw@sous-sol.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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