From: Michael Ellerman <mpe@ellerman.id.au>
To: Qian Cai <cai@lca.pw>, benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Qian Cai <cai@lca.pw>
Subject: Re: [PATCH] powerpc: fix "sz" set but not used
Date: Fri, 01 Mar 2019 14:24:16 +1100 [thread overview]
Message-ID: <87ef7rjmzj.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190228023505.80092-1-cai@lca.pw>
Qian Cai <cai@lca.pw> writes:
> arch/powerpc/mm/hugetlbpage-hash64.c: In function '__hash_page_huge':
> arch/powerpc/mm/hugetlbpage-hash64.c:29:28: warning: variable 'sz' set
> but not used [-Wunused-but-set-variable]
It's always nice to know *why* it's not used.
It's unlikely, but not impossible, that it's a bug that the variable is
not used.
To find out why:
$ git log --oneline -S sz arch/powerpc/mm/hugetlbpage-hash64.c
0895ecda7942 powerpc/mm: Bring hugepage PTE accessor functions back into sync with normal accessors
883a3e523672 powerpc/mm: Split hash MMU specific hugepage code into a new file
Then we look at those, and see the the first one did:
@@ -89,8 +62,7 @@ int __hash_page_huge(unsigned long ea, unsigned long access, unsigned long vsid,
if (!cpu_has_feature(CPU_FTR_COHERENT_ICACHE))
/* No CPU has hugepages but lacks no execute, so we
* don't need to worry about that case */
- rflags = hash_huge_page_do_lazy_icache(rflags, __pte(old_pte),
- trap, sz);
+ rflags = hash_page_do_lazy_icache(rflags, __pte(old_pte), trap);
And if you read the commit log it's pretty clear the change was
deliberate and so sz should indeed be removed.
I've applied this as-is, no need to send a v2.
cheers
> diff --git a/arch/powerpc/mm/hugetlbpage-hash64.c b/arch/powerpc/mm/hugetlbpage-hash64.c
> index 2e6a8f9345d3..f6b09edc5e6e 100644
> --- a/arch/powerpc/mm/hugetlbpage-hash64.c
> +++ b/arch/powerpc/mm/hugetlbpage-hash64.c
> @@ -26,7 +26,7 @@ int __hash_page_huge(unsigned long ea, unsigned long access, unsigned long vsid,
> real_pte_t rpte;
> unsigned long vpn;
> unsigned long old_pte, new_pte;
> - unsigned long rflags, pa, sz;
> + unsigned long rflags, pa;
> long slot, offset;
>
> BUG_ON(shift != mmu_psize_defs[mmu_psize].shift);
> @@ -73,7 +73,6 @@ int __hash_page_huge(unsigned long ea, unsigned long access, unsigned long vsid,
> offset = PTRS_PER_PMD;
> rpte = __real_pte(__pte(old_pte), ptep, offset);
>
> - sz = ((1UL) << shift);
> if (!cpu_has_feature(CPU_FTR_COHERENT_ICACHE))
> /* No CPU has hugepages but lacks no execute, so we
> * don't need to worry about that case */
> --
> 2.17.2 (Apple Git-113)
next prev parent reply other threads:[~2019-03-01 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 2:35 Qian Cai
2019-03-01 3:24 ` Michael Ellerman [this message]
2019-03-04 0:48 ` Michael Ellerman
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=87ef7rjmzj.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®