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 7/9] target-i386: check/enforce: Eliminate check_feat field
Date: Fri, 4 Jan 2013 13:37:42 -0200 [thread overview]
Message-ID: <1357313864-31026-8-git-send-email-ehabkost@redhat.com> (raw)
In-Reply-To: <1357313864-31026-1-git-send-email-ehabkost@redhat.com>
Now that all entries have check_feat=~0 on
kvm_check_features_against_host(), we can eliminate check_feat entirely
and make the code check all bits.
This patch shouldn't introduce any behavior change, as check_feat is set
to ~0 on all entries.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
target-i386/cpu.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 21aceed..05134a8 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -147,7 +147,6 @@ const char *get_register_name_32(unsigned int reg)
typedef struct model_features_t {
uint32_t *guest_feat;
uint32_t *host_feat;
- uint32_t check_feat;
const char **flag_names;
uint32_t cpuid;
int reg;
@@ -951,8 +950,7 @@ static int unavailable_host_feature(struct model_features_t *f, uint32_t mask)
}
/* best effort attempt to inform user requested cpu flags aren't making
- * their way to the guest. Note: ft[].check_feat ideally should be
- * specified via a guest_def field to suppress report of extraneous flags.
+ * their way to the guest.
*
* This function may be called only if KVM is enabled.
*/
@@ -963,20 +961,20 @@ static int kvm_check_features_against_host(x86_def_t *guest_def)
int rv, i;
struct model_features_t ft[] = {
{&guest_def->features, &host_def.features,
- ~0, feature_name, 0x00000001, R_EDX},
+ feature_name, 0x00000001, R_EDX},
{&guest_def->ext_features, &host_def.ext_features,
- ~0, ext_feature_name, 0x00000001, R_ECX},
+ ext_feature_name, 0x00000001, R_ECX},
{&guest_def->ext2_features, &host_def.ext2_features,
- ~0, ext2_feature_name, 0x80000001, R_EDX},
+ ext2_feature_name, 0x80000001, R_EDX},
{&guest_def->ext3_features, &host_def.ext3_features,
- ~0, ext3_feature_name, 0x80000001, R_ECX}};
+ ext3_feature_name, 0x80000001, R_ECX}};
assert(kvm_enabled());
kvm_cpu_fill_host(&host_def);
for (rv = 0, i = 0; i < ARRAY_SIZE(ft); ++i)
for (mask = 1; mask; mask <<= 1)
- if (ft[i].check_feat & mask && *ft[i].guest_feat & mask &&
+ if (*ft[i].guest_feat & mask &&
!(*ft[i].host_feat & mask)) {
unavailable_host_feature(&ft[i], mask);
rv = 1;
--
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 ` Eduardo Habkost [this message]
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-8-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).