From: Michael Ellerman <mpe@ellerman.id.au>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S PR: remove unused define in kvmppc_mmu_book3s_64_xlate
Date: Fri, 04 Jun 2021 11:58:58 +0000 [thread overview]
Message-ID: <87lf7pg7st.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20210604081303.3701171-1-yangerkun@huawei.com>
yangerkun <yangerkun@huawei.com> writes:
> arch/powerpc/kvm/book3s_64_mmu.c:199:6: warning: variable ‘v’ set but
> not used [-Wunused-but-set-variable]
> 199 | u64 v, r;
> | ^
>
> Fix it by remove the define.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: yangerkun <yangerkun@huawei.com>
> ---
> arch/powerpc/kvm/book3s_64_mmu.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kvm/book3s_64_mmu.c b/arch/powerpc/kvm/book3s_64_mmu.c
> index 26b8b27a3755..feee40cb2ba1 100644
> --- a/arch/powerpc/kvm/book3s_64_mmu.c
> +++ b/arch/powerpc/kvm/book3s_64_mmu.c
> @@ -196,7 +196,7 @@ static int kvmppc_mmu_book3s_64_xlate(struct kvm_vcpu *vcpu, gva_t eaddr,
> hva_t ptegp;
> u64 pteg[16];
> u64 avpn = 0;
> - u64 v, r;
> + u64 r;
> u64 v_val, v_mask;
> u64 eaddr_mask;
> int i;
> @@ -285,7 +285,6 @@ static int kvmppc_mmu_book3s_64_xlate(struct kvm_vcpu *vcpu, gva_t eaddr,
> goto do_second;
> }
>
> - v = be64_to_cpu(pteg[i]);
> r = be64_to_cpu(pteg[i+1]);
> pp = (r & HPTE_R_PP) | key;
> if (r & HPTE_R_PP0)
The obvious question being "does it not check v?!"
But we already did it further up:
for (i=0; i<16; i+=2) {
u64 pte0 = be64_to_cpu(pteg[i]);
u64 pte1 = be64_to_cpu(pteg[i + 1]);
/* Check all relevant fields of 1st dword */
if ((pte0 & v_mask) == v_val) {
...
found = true;
So I guess we don't need the value of v for anything else, so this patch
is probably good.
cheers
next prev parent reply other threads:[~2021-06-04 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 8:13 [PATCH] KVM: PPC: Book3S PR: remove unused define in kvmppc_mmu_book3s_64_xlate yangerkun
2021-06-04 11:58 ` Michael Ellerman [this message]
2021-06-15 13:50 ` yangerkun
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=87lf7pg7st.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=kvm-ppc@vger.kernel.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