From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Cc: Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Aurelien Jarno <aurelien@aurel32.net>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [qom-cpu PATCH 03/10] target-i386: Pass FeatureWord argument to report_unavailable_features()
Date: Fri, 28 Feb 2014 17:21:46 -0300 [thread overview]
Message-ID: <1393618913-12411-4-git-send-email-ehabkost@redhat.com> (raw)
In-Reply-To: <1393618913-12411-1-git-send-email-ehabkost@redhat.com>
This will help us simplify the code that calls
report_unavailable_features() later.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
target-i386/cpu.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index b46478b..af82289 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1172,8 +1172,9 @@ static void kvm_cpu_fill_host(X86CPUDefinition *x86_cpu_def)
}
}
-static int report_unavailable_features(FeatureWordInfo *f, uint32_t mask)
+static int report_unavailable_features(FeatureWord w, uint32_t mask)
{
+ FeatureWordInfo *f = &feature_word_info[w];
int i;
for (i = 0; i < 32; ++i) {
@@ -1794,7 +1795,7 @@ static int filter_features_for_kvm(X86CPU *cpu)
cpu->filtered_features[w] = requested_features & ~env->features[w];
if (cpu->filtered_features[w]) {
if (cpu->check_cpuid || cpu->enforce_cpuid) {
- report_unavailable_features(wi, cpu->filtered_features[w]);
+ report_unavailable_features(w, cpu->filtered_features[w]);
}
rv = 1;
}
--
1.8.5.3
next prev parent reply other threads:[~2014-02-28 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 20:21 [Qemu-devel] [qom-cpu PATCH 00/10] target-i386: Support check/enforce flags in TCG mode, too Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 01/10] target-i386: Simplify reporting of unavailable features Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 02/10] target-i386: Merge feature filtering/checking functions Eduardo Habkost
2014-02-28 20:21 ` Eduardo Habkost [this message]
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 04/10] target-i386: Isolate KVM-specific code on CPU feature filtering logic Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 05/10] target-i386: Make TCG feature filtering more readable Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 06/10] target-i386: Filter FEAT_7_0_EBX TCG features too Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 07/10] target-i386: Filter KVM and 0xC0000001 features on TCG Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 08/10] target-i386: Define TCG_*_FEATURES earlier on cpu.c Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 09/10] target-i386: Loop-based feature word filtering in TCG mode Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 10/10] target-i386: Support check/enforce flags in TCG mode, too Eduardo Habkost
2014-02-28 21:32 ` [Qemu-devel] [qom-cpu PATCH 00/10] " Richard Henderson
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=1393618913-12411-4-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).