From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: libvir-list@redhat.com, "Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH 8/9] target-i386: Call kvm_check_features_against_host() only if CONFIG_KVM is set
Date: Fri, 4 Jan 2013 13:37:43 -0200 [thread overview]
Message-ID: <1357313864-31026-9-git-send-email-ehabkost@redhat.com> (raw)
In-Reply-To: <1357313864-31026-1-git-send-email-ehabkost@redhat.com>
This will be necessary once kvm_check_features_against_host() starts
using KVM-specific definitions (so it won't compile anymore if
CONFIG_KVM is not set).
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
target-i386/cpu.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 05134a8..02c00bf 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -933,6 +933,7 @@ static void kvm_cpu_fill_host(x86_def_t *x86_cpu_def)
#endif /* CONFIG_KVM */
}
+#ifdef CONFIG_KVM
static int unavailable_host_feature(struct model_features_t *f, uint32_t mask)
{
int i;
@@ -981,6 +982,7 @@ static int kvm_check_features_against_host(x86_def_t *guest_def)
}
return rv;
}
+#endif
static void x86_cpuid_version_get_family(Object *obj, Visitor *v, void *opaque,
const char *name, Error **errp)
@@ -1404,10 +1406,12 @@ static int cpu_x86_parse_featurestr(x86_def_t *x86_cpu_def, char *features)
x86_cpu_def->kvm_features &= ~minus_kvm_features;
x86_cpu_def->svm_features &= ~minus_svm_features;
x86_cpu_def->cpuid_7_0_ebx_features &= ~minus_7_0_ebx_features;
+#ifdef CONFIG_KVM
if (check_cpuid && kvm_enabled()) {
if (kvm_check_features_against_host(x86_cpu_def) && enforce_cpuid)
goto error;
}
+#endif
return 0;
error:
--
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 ` [Qemu-devel] [PATCH 1/9] target-i386: kvm: -cpu host: Use GET_SUPPORTED_CPUID for SVM features Eduardo Habkost
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 ` Eduardo Habkost [this message]
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-9-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@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).