From: Paolo Bonzini <pbonzini@redhat.com>
To: Jinrong Liang <ljr.kernel@gmail.com>
Cc: Wanpeng Li <wanpengli@tencent.com>,
Sean Christopherson <seanjc@google.com>,
Jim Mattson <jmattson@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Joerg Roedel <joro@8bytes.org>,
Jinrong Liang <cloudliang@tencent.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: kvm/x86: Fix the warning in pmu_event_filter_test.c
Date: Wed, 19 Jan 2022 19:37:26 +0100 [thread overview]
Message-ID: <06e16701-1380-8186-2f21-e5cc5a5c8467@redhat.com> (raw)
In-Reply-To: <20220119133910.56285-1-cloudliang@tencent.com>
On 1/19/22 14:39, Jinrong Liang wrote:
> From: Jinrong Liang <cloudliang@tencent.com>
>
> The following warning appears when executing
> make -C tools/testing/selftests/kvm
>
> x86_64/pmu_event_filter_test.c: In function ‘vcpu_supports_intel_br_retired’:
> x86_64/pmu_event_filter_test.c:241:28: warning: variable ‘cpuid’ set but not used [-Wunused-but-set-variable]
> 241 | struct kvm_cpuid2 *cpuid;
> | ^~~~~
> x86_64/pmu_event_filter_test.c: In function ‘vcpu_supports_amd_zen_br_retired’:
> x86_64/pmu_event_filter_test.c:258:28: warning: variable ‘cpuid’ set but not used [-Wunused-but-set-variable]
> 258 | struct kvm_cpuid2 *cpuid;
> | ^~~~~
>
> Just delete the unused variables to stay away from warnings.
>
> Fixes: dc7e75b3b3ee ("selftests: kvm/x86: Add test for KVM_SET_PMU_EVENT_FILTER")
> Signed-off-by: Jinrong Liang <cloudliang@tencent.com>
> ---
> tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c b/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c
> index 8ac99d4cbc73..0611a5c24bbc 100644
> --- a/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c
> +++ b/tools/testing/selftests/kvm/x86_64/pmu_event_filter_test.c
> @@ -238,9 +238,7 @@ static void test_not_member_allow_list(struct kvm_vm *vm)
> static bool vcpu_supports_intel_br_retired(void)
> {
> struct kvm_cpuid_entry2 *entry;
> - struct kvm_cpuid2 *cpuid;
>
> - cpuid = kvm_get_supported_cpuid();
> entry = kvm_get_supported_cpuid_index(0xa, 0);
> return entry &&
> (entry->eax & 0xff) &&
> @@ -255,9 +253,7 @@ static bool vcpu_supports_intel_br_retired(void)
> static bool vcpu_supports_amd_zen_br_retired(void)
> {
> struct kvm_cpuid_entry2 *entry;
> - struct kvm_cpuid2 *cpuid;
>
> - cpuid = kvm_get_supported_cpuid();
> entry = kvm_get_supported_cpuid_index(1, 0);
> return entry &&
> ((x86_family(entry->eax) == 0x17 &&
Queued, thanks.
Paolo
prev parent reply other threads:[~2022-01-19 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 13:39 Jinrong Liang
2022-01-19 18:37 ` Paolo Bonzini [this message]
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=06e16701-1380-8186-2f21-e5cc5a5c8467@redhat.com \
--to=pbonzini@redhat.com \
--cc=cloudliang@tencent.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljr.kernel@gmail.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
Powered by JetHome