From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, "Gleb Natapov" <gleb@redhat.com>,
libvir-list@redhat.com, "Joerg Roedel" <joro@8bytes.org>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 1/9] target-i386: kvm: -cpu host: Use GET_SUPPORTED_CPUID for SVM features
Date: Fri, 4 Jan 2013 13:37:36 -0200 [thread overview]
Message-ID: <1357313864-31026-2-git-send-email-ehabkost@redhat.com> (raw)
In-Reply-To: <1357313864-31026-1-git-send-email-ehabkost@redhat.com>
The existing -cpu host code simply set every bit inside svm_features
(initializing it to -1), and that makes it impossible to make the
enforce/check options work properly when the user asks for SVM features
explicitly in the command-line.
So, instead of initializing svm_features to -1, use GET_SUPPORTED_CPUID
to fill only the bits that are supported by the host (just like we do
for all other CPUID feature words inside kvm_cpu_fill_host()).
This will keep the existing behavior (as filter_features_for_kvm()
already uses GET_SUPPORTED_CPUID to filter svm_features), but will allow
us to properly check for KVM features inside
kvm_check_features_against_host() later.
For example, we will be able to make this:
$ qemu-system-x86_64 -cpu ...,+pfthreshold,enforce
refuse to start if the SVM "pfthreshold" feature is not supported by the
host (after we fix kvm_check_features_against_host() to check SVM flags
as well).
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
Changes v2:
- Coding style (indentation) fix
Cc: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Joerg Roedel <joro@8bytes.org>
Cc: kvm@vger.kernel.org
---
target-i386/cpu.c | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index ec877c7..649cfb2 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -906,13 +906,10 @@ static void kvm_cpu_fill_host(x86_def_t *x86_cpu_def)
}
}
- /*
- * Every SVM feature requires emulation support in KVM - so we can't just
- * read the host features here. KVM might even support SVM features not
- * available on the host hardware. Just set all bits and mask out the
- * unsupported ones later.
- */
- x86_cpu_def->svm_features = -1;
+ /* Other KVM-specific feature fields: */
+ x86_cpu_def->svm_features =
+ kvm_arch_get_supported_cpuid(s, 0x8000000A, 0, R_EDX);
+
#endif /* CONFIG_KVM */
}
--
1.7.11.7
next prev parent reply other threads:[~2013-01-04 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 15:37 [Qemu-devel] [PATCH 0/9] target-i386: make "enforce" flag work as it should Eduardo Habkost
2013-01-04 15:37 ` Eduardo Habkost [this message]
2013-01-04 15:37 ` [Qemu-devel] [PATCH 2/9] target-i386: kvm: Enable all supported KVM features for -cpu host Eduardo Habkost
2013-01-04 15:37 ` [Qemu-devel] [PATCH 3/9] target-i386: check/enforce: Fix CPUID leaf numbers on error messages Eduardo Habkost
2013-01-04 20:54 ` Blue Swirl
2013-01-04 15:37 ` [Qemu-devel] [PATCH 4/9] target-i386: check/enforce: Do not ignore "hypervisor" flag Eduardo Habkost
2013-01-04 15:37 ` [Qemu-devel] [PATCH 5/9] target-i386: check/enforce: Check all CPUID.80000001H.EDX bits Eduardo Habkost
2013-01-04 15:37 ` [Qemu-devel] [PATCH 6/9] target-i386: check/enforce: Check SVM flag support as well Eduardo Habkost
2013-01-04 15:37 ` [Qemu-devel] [PATCH 7/9] target-i386: check/enforce: Eliminate check_feat field Eduardo Habkost
2013-01-04 15:37 ` [Qemu-devel] [PATCH 8/9] target-i386: Call kvm_check_features_against_host() only if CONFIG_KVM is set Eduardo Habkost
2013-01-04 15:37 ` [Qemu-devel] [PATCH 9/9] target-i386: check/enforce: Check all feature words Eduardo Habkost
[not found] ` <201301042020.r04KKv0R014816@d01av02.pok.ibm.com>
2013-01-04 20:48 ` [Qemu-devel] [PATCH 0/9] target-i386: make "enforce" flag work as it should Eduardo Habkost
2013-01-04 21:10 ` Anthony Liguori
2013-01-04 21:00 ` Anthony Liguori
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=1357313864-31026-2-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=mtosatti@redhat.com \
--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).