From: Gavin Shan <gshan@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, ryan.roberts@arm.com, peterx@redhat.com,
joey.gouly@arm.com, yangyicong@hisilicon.com,
shan.gavin@gmail.com
Subject: Re: [PATCH] arm64: mm: Drop duplicate check in pmd_trans_huge()
Date: Thu, 8 May 2025 18:56:17 +1000 [thread overview]
Message-ID: <fdeff5e5-daab-4967-a6bf-f71efd78507c@redhat.com> (raw)
In-Reply-To: <4e5941f8-7e61-4a63-a669-bee1601093a6@arm.com>
On 5/8/25 3:44 PM, Anshuman Khandual wrote:
> On 5/8/25 09:21, Gavin Shan wrote:
>> pmd_val(pmd) is inclusive to pmd_present(pmd) since the PMD entry
>> value isn't zero when pmd_present() returns true. Just drop the
>> duplicate check done by pmd_val(pmd).
>
> Agreed, pmd_val() is redundant here because a positive pmd_present()
> also ensures a positive pmd_val().
>
> #define pmd_present(pmd) pte_present(pmd_pte(pmd))
> #define pte_present(pte) (pte_valid(pte) || pte_present_invalid(pte))
>
> #define pte_valid(pte) (!!(pte_val(pte) & PTE_VALID))
> #define pte_present_invalid(pte) ((pte_val(pte) & (PTE_VALID |
> PTE_PRESENT_INVALID)) == PTE_PRESENT_INVALID)
>
> pte_present() cannot return positive here unless either of the flags
> PTE_VALID or PTE_PRESENT_INVALID is set which implies pte_val() would
> also return positive.
>
> Probably it would be better to add the above details in the commit
> message here as well.
>
Thanks, I've squashed those details to v2, which was just posted.
> The earlier commit skipped dropping pmd_val() in order to keep then
> proposed change confined to just adding new pmd_table() check, even
> though pmd_val() redundancy was evident as well which should have
> been dropped there after.
>
> d1770e909898 ("arm64/mm: Check pmd_table() in pmd_trans_huge()")
>
Yes, agreed.
>>
>> No functional changes intended.
>>
>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>> ---
>> Found this by code inspection
>> ---
>> arch/arm64/include/asm/pgtable.h | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
>> index d3b538be1500..2599b9b8666f 100644
>> --- a/arch/arm64/include/asm/pgtable.h
>> +++ b/arch/arm64/include/asm/pgtable.h
>> @@ -739,8 +739,7 @@ static inline int pmd_trans_huge(pmd_t pmd)
>> * If pmd is present-invalid, pmd_table() won't detect it
>> * as a table, so force the valid bit for the comparison.
>> */
>> - return pmd_val(pmd) && pmd_present(pmd) &&
>> - !pmd_table(__pmd(pmd_val(pmd) | PTE_VALID));
>> + return pmd_present(pmd) && !pmd_table(__pmd(pmd_val(pmd) | PTE_VALID));
>> }
>> #endif /* CONFIG_TRANSPARENT_HUGEPAGE */
>>
> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
>
Thanks,
Gavin
prev parent reply other threads:[~2025-05-08 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 3:51 Gavin Shan
2025-05-08 4:00 ` Dev Jain
2025-05-08 5:44 ` Anshuman Khandual
2025-05-08 8:56 ` Gavin Shan [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=fdeff5e5-daab-4967-a6bf-f71efd78507c@redhat.com \
--to=gshan@redhat.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shan.gavin@gmail.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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
all inboxes | Powered by JetHome®