From: Don Slutz <Don@CloudSwitch.com>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org, mtosatti@redhat.com,
ehabkost@redhat.com, imammedo@redhat.com, avi@redhat.com,
afaerber@suse.de, peter.maydell@linaro.org,
anthony@codemonkey.ws
Cc: Don Slutz <Don@CloudSwitch.com>
Subject: [Qemu-devel] [PATCH v7 15/17] target-i386: Use Hypervisor level in -machine pc, accel=tcg.
Date: Fri, 12 Oct 2012 15:56:20 -0400 [thread overview]
Message-ID: <1350071782-23078-16-git-send-email-Don@CloudSwitch.com> (raw)
In-Reply-To: <1350071782-23078-1-git-send-email-Don@CloudSwitch.com>
Part of "target-i386: Add way to expose VMWare CPUID"
Also known as Paravirtualization level.
QEMU knows this as KVM_CPUID_SIGNATURE (0x40000000) in kvm on linux.
This does not provide vendor support in tcg yet.
>From http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00100.html
kvm has this issue:
"Note also that old hosts set eax value to 0x0. This should
be interpreted as if the value was 0x40000001."
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Also:
http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00100.html
VMware documention on CPUIDs (Mechanisms to determine if software is
running in a VMware virtual machine):
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009458
Signed-off-by: Don Slutz <Don@CloudSwitch.com>
---
target-i386/cpu.c | 30 ++++++++++++++++++++++++++++++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index c8466ec..5b33b95 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1767,6 +1767,24 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
index = env->cpuid_xlevel;
}
}
+ } else if (index & 0x40000000) {
+ /* test if maximum index reached
+ * but only if Hypervisor level is set */
+ if (env->cpuid_hv_level_set) {
+ uint32_t real_level = env->cpuid_hv_level;
+
+ /* Handle Hypervisor CPUIDs.
+ * kvm defines 0 to be the same as 0x40000001 */
+ if (real_level < 0x40000000) {
+ real_level = 0x40000001;
+ }
+ if (index > real_level) {
+ index = real_level;
+ }
+ } else {
+ if (index > env->cpuid_level)
+ index = env->cpuid_level;
+ }
} else {
if (index > env->cpuid_level)
index = env->cpuid_level;
@@ -1905,6 +1923,18 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
*edx = 0;
}
break;
+ case 0x40000000:
+ *eax = env->cpuid_hv_level;
+ *ebx = 0;
+ *ecx = 0;
+ *edx = 0;
+ break;
+ case 0x40000001:
+ *eax = env->cpuid_kvm_features;
+ *ebx = 0;
+ *ecx = 0;
+ *edx = 0;
+ break;
case 0x80000000:
*eax = env->cpuid_xlevel;
*ebx = env->cpuid_vendor1;
--
1.7.1
next prev parent reply other threads:[~2012-10-12 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 19:56 [Qemu-devel] [PATCH v7 00/17] target-i386: Add way to expose VMWare CPUID Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 01/17] target-i386: Add Hypervisor level Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 02/17] target-i386: Add Hypervisor vendor Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 03/17] target-i386: Add Hypervisor features Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 04/17] target-i386: Add cpu object access routines for Hypervisor level Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 05/17] target-i386: Add cpu object access routines for Hypervisor vendor Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 06/17] target-i386: Add cpu object access routines for Hypervisor features Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 07/17] target-i386: Add x86_set_hyperv Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 08/17] target-i386: Use x86_set_hyperv to set hypervisor vendor Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 09/17] target-i386: Use x86_set_hyperv to set hypervisor features Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 10/17] target-i386: Use Hypervisor level in -machine pc, accel=kvm Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 11/17] target-i386: Use Hypervisor vendor " Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 12/17] target-i386: Use Hypervisor features " Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 13/17] target-i386: Add VMWare CPUID Timing information " Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 14/17] target-i386: Add vmare as a known name to Hypervisor vendor Don Slutz
2012-10-12 19:56 ` Don Slutz [this message]
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 16/17] target-i386: Use Hypervisor vendor in -machine pc, accel=tcg Don Slutz
2012-10-12 19:56 ` [Qemu-devel] [PATCH v7 17/17] target-i386: target-i386: Add VMWare CPUID Timing information " Don Slutz
2012-10-29 20:39 ` [Qemu-devel] [PATCH v7 00/17] target-i386: Add way to expose VMWare CPUID Marcelo Tosatti
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=1350071782-23078-16-git-send-email-Don@CloudSwitch.com \
--to=don@cloudswitch.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).