All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	KY Srinivasan <kys@microsoft.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"gleb@redhat.com" <gleb@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] x86: properly handle kvm emulation of hyperv
Date: Thu, 25 Jul 2013 16:12:49 +0800	[thread overview]
Message-ID: <51F0DE01.50607@redhat.com> (raw)
In-Reply-To: <51F0DAD1.8080108@redhat.com>

On 07/25/2013 03:59 PM, Paolo Bonzini wrote:
> Il 24/07/2013 23:37, H. Peter Anvin ha scritto:
>> What I'm suggesting is exactly that except that the native hypervisor is later in CPUID space.
> Me too actually.
>
> I was just suggesting an implementation of the idea (that takes into
> account hypervisors detected by other means than CPUID).
>
> Paolo

This make sense, will send V2.

Thanks
>> KY Srinivasan <kys@microsoft.com> wrote:
>>> As Paolo suggested if there were some priority encoded, the guest could make an
>>> informed decision. If the guest under question can run on both hypervisors A and B,
>>> we would rather the guest discover hypervisor A when running on A and
>>> hypervisor B when running on B. The priority encoding could be as simple as
>>> surfacing the native hypervisor signature earlier in the CPUID space.


  reply	other threads:[~2013-07-25  8:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23  9:41 [PATCH 1/4] x86: introduce hypervisor_cpuid_base() Jason Wang
2013-07-23  9:41 ` [PATCH 2/4] xen: switch to use hypervisor_cpuid_base() Jason Wang
2013-07-23  9:41   ` Jason Wang
2013-07-23 11:16   ` Paolo Bonzini
2013-07-23 11:16     ` Paolo Bonzini
2013-07-23 15:55   ` Konrad Rzeszutek Wilk
2013-07-23 15:55     ` Konrad Rzeszutek Wilk
2013-07-23  9:41 ` [PATCH 3/4] kvm: " Jason Wang
2013-07-23 11:16   ` Paolo Bonzini
2013-07-23  9:41 ` [PATCH 4/4] x86: properly handle kvm emulation of hyperv Jason Wang
2013-07-23 11:17   ` Paolo Bonzini
2013-07-23 13:55   ` KY Srinivasan
2013-07-23 14:48     ` H. Peter Anvin
2013-07-23 17:45       ` KY Srinivasan
2013-07-23 18:45         ` H. Peter Anvin
2013-07-23 22:42           ` KY Srinivasan
2013-07-24  4:37       ` Jason Wang
2013-07-24  4:48         ` H. Peter Anvin
2013-07-24  6:54           ` Jason Wang
2013-07-24  7:06             ` Paolo Bonzini
2013-07-24 14:01               ` KY Srinivasan
2013-07-24 15:14                 ` H. Peter Anvin
2013-07-24 19:05                   ` KY Srinivasan
2013-07-24 19:05                     ` KY Srinivasan
2013-07-24 21:37                     ` H. Peter Anvin
2013-07-25  7:59                       ` Paolo Bonzini
2013-07-25  8:12                         ` Jason Wang [this message]
2013-07-23 10:04 ` [PATCH 1/4] x86: introduce hypervisor_cpuid_base() H. Peter Anvin
2013-07-23 11:16   ` Paolo Bonzini
2013-07-23 16:03     ` H. Peter Anvin
2013-07-24  4:44       ` Jason Wang
2013-07-24  4:47         ` H. Peter Anvin
2013-07-23 13:48 ` Gleb Natapov
2013-07-24  4:34   ` Jason Wang

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=51F0DE01.50607@redhat.com \
    --to=jasowang@redhat.com \
    --cc=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --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.