From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Lei Wang <lei4.wang@intel.com>, pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, imammedo@redhat.com, dgilbert@redhat.com,
berrange@redhat.com, yang.zhong@linux.intel.com
Subject: Re: [PATCH v3 2/6] i386: Remove unused parameter "uint32_t bit" in feature_word_description()
Date: Wed, 8 Feb 2023 22:33:02 +0800 [thread overview]
Message-ID: <0ffc69e1-5b2f-d8f9-ff45-cfd0cb0357da@intel.com> (raw)
In-Reply-To: <20230106083826.5384-3-lei4.wang@intel.com>
On 1/6/2023 4:38 PM, Lei Wang wrote:
> Parameter "uint32_t bit" is not used in function feature_word_description(),
> so remove it.
>
> Signed-off-by: Lei Wang <lei4.wang@intel.com>
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
> ---
> target/i386/cpu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index b6d1247e5e..883098bc5a 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -4290,7 +4290,7 @@ static const TypeInfo max_x86_cpu_type_info = {
> .class_init = max_x86_cpu_class_init,
> };
>
> -static char *feature_word_description(FeatureWordInfo *f, uint32_t bit)
> +static char *feature_word_description(FeatureWordInfo *f)
> {
> assert(f->type == CPUID_FEATURE_WORD || f->type == MSR_FEATURE_WORD);
>
> @@ -4329,6 +4329,7 @@ static void mark_unavailable_features(X86CPU *cpu, FeatureWord w, uint64_t mask,
> CPUX86State *env = &cpu->env;
> FeatureWordInfo *f = &feature_word_info[w];
> int i;
> + g_autofree char *feat_word_str = feature_word_description(f);
>
> if (!cpu->force_features) {
> env->features[w] &= ~mask;
> @@ -4341,7 +4342,6 @@ static void mark_unavailable_features(X86CPU *cpu, FeatureWord w, uint64_t mask,
>
> for (i = 0; i < 64; ++i) {
> if ((1ULL << i) & mask) {
> - g_autofree char *feat_word_str = feature_word_description(f, i);
> warn_report("%s: %s%s%s [bit %d]",
> verbose_prefix,
> feat_word_str,
next prev parent reply other threads:[~2023-02-08 14:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 8:38 [PATCH v3 0/6] Support for new CPU model SapphireRapids Lei Wang
2023-01-06 8:38 ` [PATCH v3 1/6] i386: Introduce FeatureWordInfo for AMX CPUID leaf 0x1D and 0x1E Lei Wang
2023-02-06 7:45 ` Yuan Yao
2023-01-06 8:38 ` [PATCH v3 2/6] i386: Remove unused parameter "uint32_t bit" in feature_word_description() Lei Wang
2023-01-27 13:29 ` Igor Mammedov
2023-02-08 14:33 ` Xiaoyao Li [this message]
2023-01-06 8:38 ` [PATCH v3 3/6] i386: Introduce new struct "MultiBitFeatureInfo" for multi-bit features Lei Wang
2023-02-08 14:39 ` Xiaoyao Li
2023-01-06 8:38 ` [PATCH v3 4/6] i386: Mask and report unavailable multi-bit feature values Lei Wang
2023-02-06 7:43 ` Yuan Yao
2023-02-09 1:04 ` Wang, Lei
2023-02-09 3:29 ` Xiaoyao Li
2023-02-09 4:21 ` Wang, Lei
2023-02-09 5:59 ` Xiaoyao Li
2023-02-09 6:15 ` Wang, Lei
2023-02-09 9:26 ` Xiaoyao Li
2023-01-06 8:38 ` [PATCH v3 5/6] i386: Initialize AMX CPUID leaves with corresponding env->features[] leaves Lei Wang
2023-01-06 8:38 ` [PATCH v3 6/6] i386: Add new CPU model SapphireRapids Lei Wang
2023-02-02 10:40 ` Igor Mammedov
2023-02-03 6:02 ` Wang, Lei
2023-02-02 11:05 ` [PATCH v3 0/6] Support for " Igor Mammedov
2023-02-07 2:50 ` Wang, Lei
2023-03-06 12:49 ` Igor Mammedov
2023-02-08 14:53 ` Xiaoyao Li
2023-03-02 14:49 ` Robert Hoo
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=0ffc69e1-5b2f-d8f9-ff45-cfd0cb0357da@intel.com \
--to=xiaoyao.li@intel.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=lei4.wang@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yang.zhong@linux.intel.com \
/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).