public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	akataria@vmware.com
Subject: Re: [PATCH -tip] x86: move vmware to hypervisor
Date: Tue, 17 Mar 2009 08:50:35 -0700	[thread overview]
Message-ID: <49BFC6CB.9070603@zytor.com> (raw)
In-Reply-To: <1237283318.7907.9.camel@ht.satnam>

Jaswinder Singh Rajput wrote:
>> I dont really like this one. KVM is a hypervisor too, and so is 
>> Xen and lguest. VMware is one of the many types of a 
>> hypervisors.
> 
> Can we use common hypervisor for Xen, lguest, vmware, etc.
> And Xen, lguest, vmware will be the sub-options.

Obviously.  We spent a lot of time breaking up the cpu stuff into common
and vendor-specific portions, we shouldn't go backwards w.r.t. hypervisors.
	
	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2009-03-17 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  9:19 [PATCH -tip] x86: move vmware to hypervisor Jaswinder Singh Rajput
2009-03-17  9:39 ` Ingo Molnar
2009-03-17  9:48   ` Jaswinder Singh Rajput
2009-03-17 15:50     ` H. Peter Anvin [this message]
2009-03-25  5:29       ` Jaswinder Singh Rajput
2009-03-25 12:59         ` Ingo Molnar
2009-03-25 16:52           ` Alok Kataria
2009-03-25 17:07             ` Jaswinder Singh Rajput
2009-03-25 17:24               ` Alok Kataria
2009-03-25 17:38                 ` Jaswinder Singh Rajput
2009-03-25 18:18                   ` Alok Kataria
2009-03-26  7:10                     ` david
2009-03-26 16:40                       ` Alok Kataria
2009-03-27  0:10                         ` H. Peter Anvin
2009-03-25 13:38         ` Mark Lord
2009-03-17 17:28 ` 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=49BFC6CB.9070603@zytor.com \
    --to=hpa@zytor.com \
    --cc=akataria@vmware.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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