From: Avi Kivity <avi@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Alok Kataria <akataria@vmware.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.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: Sun, 20 Sep 2009 22:00:00 +0300 [thread overview]
Message-ID: <4AB67BB0.3020303@redhat.com> (raw)
In-Reply-To: <4AB64EFC.10707@goop.org>
On 09/20/2009 06:49 PM, Jeremy Fitzhardinge wrote:
>> kvm will be removing the pvmmu support soon; and Xen is talking about
>> running paravirtualized guests in a vmx/svm container where they don't
>> need most of the hooks.
>>
>>
> We have no plans to drop support for non-vmx/svm capable processors, let
> alone require ept/npt.
>
Today, certainly; similarly kvm will host-side pvmmu support for a while
to support live migration from older hosts.
But in a few years it may make sense to run everything in a vmx/svm
container even for Xen; we can then drop x86 pv_ops for good.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>,
the arch/x86 maintainers <x86@kernel.org>,
Alok Kataria <akataria@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: Paravirtualization on VMware's Platform [VMI].
Date: Sun, 20 Sep 2009 22:00:00 +0300 [thread overview]
Message-ID: <4AB67BB0.3020303@redhat.com> (raw)
In-Reply-To: <4AB64EFC.10707@goop.org>
On 09/20/2009 06:49 PM, Jeremy Fitzhardinge wrote:
>> kvm will be removing the pvmmu support soon; and Xen is talking about
>> running paravirtualized guests in a vmx/svm container where they don't
>> need most of the hooks.
>>
>>
> We have no plans to drop support for non-vmx/svm capable processors, let
> alone require ept/npt.
>
Today, certainly; similarly kvm will host-side pvmmu support for a while
to support live migration from older hosts.
But in a few years it may make sense to run everything in a vmx/svm
container even for Xen; we can then drop x86 pv_ops for good.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-09-20 19:02 UTC|newest]
Thread overview: 50+ 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 [this message]
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 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 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
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 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=4AB67BB0.3020303@redhat.com \
--to=avi@redhat.com \
--cc=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=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 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.