From: Don Slutz <Don@CloudSwitch.com>
To: qemu-devel@nongnu.org, mtosatti@redhat.com, ehabkost@redhat.com,
imammedo@redhat.com, avi@redhat.com, afaerber@suse.de,
peter.maydell@linaro.org, kvm@vger.kernel.org,
anthony@codemonkey.ws
Cc: Don Slutz <Don@CloudSwitch.com>
Subject: [Qemu-devel] [PATCH v4 03/17] target-i386: Add Hypervisor level.
Date: Thu, 20 Sep 2012 16:03:18 -0400 [thread overview]
Message-ID: <1348171412-23669-4-git-send-email-Don@CloudSwitch.com> (raw)
In-Reply-To: <1348171412-23669-1-git-send-email-Don@CloudSwitch.com>
Also known as Paravirtualization level or maximim cpuid function present in this leaf.
This is just the EAX value for 0x40000000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x40000000).
This 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
QEMU has the value HYPERV_CPUID_MIN defined.
Signed-off-by: Don Slutz <Don@CloudSwitch.com>
---
target-i386/cpu.h | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index 5265c5a..05c0848 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -782,6 +782,8 @@ typedef struct CPUX86State {
uint32_t cpuid_ext4_features;
/* Flags from CPUID[EAX=7,ECX=0].EBX */
uint32_t cpuid_7_0_ebx;
+ /* Hypervisor CPUIDs */
+ uint32_t cpuid_hv_level;
/* MTRRs */
uint64_t mtrr_fixed[11];
--
1.7.1
next prev parent reply other threads:[~2012-09-20 20:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 20:03 [Qemu-devel] [PATCH v4 00/17] Allow changing of Hypervisor CPUIDs Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 01/17] target-i386: Allow tsc-frequency to be larger then 2.147G Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 02/17] target-i386: Add missing kvm bits Don Slutz
2012-09-21 8:39 ` Igor Mammedov
2012-09-21 12:36 ` Eduardo Habkost
2012-09-21 13:17 ` Don Slutz
2012-09-20 20:03 ` Don Slutz [this message]
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 04/17] target-i386: Add cpu object access routines for Hypervisor level Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 05/17] target-i386: Add x86_set_hyperv Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 06/17] target-i386: Use Hypervisor level in -machine pc, accel=kvm Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 07/17] target-i386: Use Hypervisor level in -machine pc, accel=tcg Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 08/17] target-i386: Add Hypervisor vendor Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 09/17] target-i386: Add cpu object access routines for " Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 10/17] target-i386: Use Hypervisor vendor in -machine pc, accel=kvm Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 11/17] target-i386: Use Hypervisor vendor in -machine pc, accel=tcg Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 12/17] target-i386: Add some known names to Hypervisor vendor Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 13/17] target-i386: Add optional Hypervisor leaf extra Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 14/17] target-i386: Add cpu object access routines for " Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 15/17] target-i386: Add setting of Hypervisor leaf extra for known vmare4 Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 16/17] target-i386: Use Hypervisor leaf extra in -machine pc, accel=kvm Don Slutz
2012-09-20 20:03 ` [Qemu-devel] [PATCH v4 17/17] target-i386: Use Hypervisor leaf extra in -machine pc, accel=tcg Don Slutz
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=1348171412-23669-4-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).