From: Muhammad Usama Anjum <usama.anjum@arm.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Cc: usama.anjum@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [PATCH 2/6] arm64: use hw_pte_val for HW PTE atomics
Date: Mon, 21 Sep 2026 09:49:47 +0100 [thread overview]
Message-ID: <de9380da-9b3b-4c60-9dfe-45775b3fb889@arm.com> (raw)
In-Reply-To: <f9a7cd29-8aa3-4436-a95e-999c03aad0d7@arm.com>
On 18/09/2026 4:55 pm, Ryan Roberts wrote:
> On 14/09/2026 14:51, Muhammad Usama Anjum wrote:
>> Add hw_pte_val() to preserve an lvalue for the HW PTE bits, so atomic
>> updates can take their address. pte_val() expects a SW PTE value and
>> cannot operate directly on a distinct hw_pte_t.
>>
>> With ARCH_HAS_HW_PTE_T, use pte_val() on the wrapper's __pte member;
>> otherwise, use pte_val() directly.
>>
>> The atomic operations and their ordering are unchanged.
>>
>> Signed-off-by: Muhammad Usama Anjum <usama.anjum@arm.com>
>> ---
>> arch/arm64/include/asm/pgtable.h | 10 +++++-----
>> arch/arm64/mm/fault.c | 6 +++---
>> include/linux/pgtable_types.h | 4 ++++
>> 3 files changed, 12 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
>> index 652ce413be389..4768ec59de555 100644
>> --- a/arch/arm64/include/asm/pgtable.h
>> +++ b/arch/arm64/include/asm/pgtable.h
>> @@ -1303,7 +1303,7 @@ static inline bool __ptep_test_and_clear_young(struct vm_area_struct *vma,
>> do {
>> old_pte = pte;
>> pte = pte_mkold(pte);
>> - pte_val(pte) = cmpxchg_relaxed(&pte_val(*ptep),
>> + pte_val(pte) = cmpxchg_relaxed(&hw_pte_val(*ptep),
>> pte_val(old_pte), pte_val(pte));
>> } while (pte_val(pte) != pte_val(old_pte));
>>
>> @@ -1346,7 +1346,7 @@ static inline pte_t __ptep_get_and_clear_anysz(struct mm_struct *mm,
>> hw_pte_t *ptep,
>> unsigned long pgsize)
>> {
>> - pte_t pte = __pte(xchg_relaxed(&pte_val(*ptep), 0));
>> + pte_t pte = __pte(xchg_relaxed(&hw_pte_val(*ptep), 0));
>>
>> switch (pgsize) {
>> case PAGE_SIZE:
>> @@ -1422,7 +1422,7 @@ static inline void ___ptep_set_wrprotect(struct mm_struct *mm,
>> do {
>> old_pte = pte;
>> pte = pte_wrprotect(pte);
>> - pte_val(pte) = cmpxchg_relaxed(&pte_val(*ptep),
>> + pte_val(pte) = cmpxchg_relaxed(&hw_pte_val(*ptep),
>> pte_val(old_pte), pte_val(pte));
>> } while (pte_val(pte) != pte_val(old_pte));
>> }
>> @@ -1460,7 +1460,7 @@ static inline void __clear_young_dirty_pte(struct vm_area_struct *vma,
>> if (flags & CYDP_CLEAR_DIRTY)
>> pte = pte_mkclean(pte);
>>
>> - pte_val(pte) = cmpxchg_relaxed(&pte_val(*ptep),
>> + pte_val(pte) = cmpxchg_relaxed(&hw_pte_val(*ptep),
>> pte_val(old_pte), pte_val(pte));
>> } while (pte_val(pte) != pte_val(old_pte));
>> }
>> @@ -1830,7 +1830,7 @@ static inline bool ptep_try_set(hw_pte_t *ptep, pte_t new_pte)
>> {
>> pteval_t old = 0;
>>
>> - if (!try_cmpxchg(&pte_val(*ptep), &old, pte_val(new_pte)))
>> + if (!try_cmpxchg(&hw_pte_val(*ptep), &old, pte_val(new_pte)))
>> return false;
>>
>> /*
>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
>> index b77f4be88e3ea..7d6c30f27214e 100644
>> --- a/arch/arm64/mm/fault.c
>> +++ b/arch/arm64/mm/fault.c
>> @@ -225,8 +225,8 @@ int __ptep_set_access_flags_anysz(struct vm_area_struct *vma,
>> /*
>> * Setting the flags must be done atomically to avoid racing with the
>> * hardware update of the access/dirty state. The PTE_RDONLY bit must
>> - * be set to the most permissive (lowest value) of *ptep and entry
>> - * (calculated as: a & b == ~(~a | ~b)).
>> + * be set to the most permissive (lowest value) of the current PTE and
>> + * entry (calculated as: a & b == ~(~a | ~b)).
>
> This seems like an unrelated and unecessary comment change?
I'm trying to replace *ptep with current PTE for consistency. I'll drop this
change.
>
>> */
>> pte_val(entry) ^= PTE_RDONLY;
>> pteval = pte_val(pte);
>> @@ -235,7 +235,7 @@ int __ptep_set_access_flags_anysz(struct vm_area_struct *vma,
>> pteval ^= PTE_RDONLY;
>> pteval |= pte_val(entry);
>> pteval ^= PTE_RDONLY;
>> - pteval = cmpxchg_relaxed(&pte_val(*ptep), old_pteval, pteval);
>> + pteval = cmpxchg_relaxed(&hw_pte_val(*ptep), old_pteval, pteval);
>> } while (pteval != old_pteval);
>>
>> /*
>> diff --git a/include/linux/pgtable_types.h b/include/linux/pgtable_types.h
>> index d6c5a7548550b..ee4eace5c3e1c 100644
>> --- a/include/linux/pgtable_types.h
>> +++ b/include/linux/pgtable_types.h
>> @@ -9,9 +9,13 @@
>> #ifdef CONFIG_ARCH_HAS_HW_PTE_T
>> typedef struct __hw_pte_t { pte_t __pte; } hw_pte_t;
>> #define __pte_from_hw(pte) ((pte).__pte)
>> +
>
> nit: why the newline here (and equivalent below)?
I'll drop the newlines.
>
>> +#define hw_pte_val(x) pte_val((x).__pte)
>
> Wouldn't it be better to add these as part of the generic series? I know we
> prefer to add an api along with its first user, but in this case it seems odd,
> because you're effectively requiring that arm64 is the first merged arch to
> support this? You could also use the same argument to say that none of this
> should be merged until the commit where an arch turns on ARCH_HAS_HW_PTE_T.
Agreed. Thanks for explaining. I'll move the definition to the generic series.
>
> Thanks,
> Ryan
>
>
>> #else
>> #define hw_pte_t pte_t
>> #define __pte_from_hw(pte) (pte)
>> +
>> +#define hw_pte_val(x) pte_val(x)
>> #endif
>>
>> #endif /* !__ASSEMBLY__ */
>>
>
--
Thanks,
Usama
next prev parent reply other threads:[~2026-09-21 8:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:51 [PATCH 0/6] arm64: distinguish HW PTE pointers from SW PTE value pointers Muhammad Usama Anjum
2026-09-14 13:51 ` [PATCH 1/6] arm64: use hw_pte_t for HW PTE pointers Muhammad Usama Anjum
2026-09-21 7:59 ` Ryan Roberts
2026-09-21 8:20 ` Muhammad Usama Anjum
2026-09-14 13:51 ` [PATCH 2/6] arm64: use hw_pte_val for HW PTE atomics Muhammad Usama Anjum
2026-09-18 15:55 ` Ryan Roberts
2026-09-21 8:49 ` Muhammad Usama Anjum [this message]
2026-09-14 13:51 ` [PATCH 3/6] arm64: convert between HW PTEs and SW PTE values Muhammad Usama Anjum
2026-09-18 15:56 ` Ryan Roberts
2026-09-21 8:26 ` Ryan Roberts
2026-09-21 9:50 ` Muhammad Usama Anjum
2026-09-14 13:51 ` [PATCH 4/6] arm64: use hw_pte_t for fixmap HW PTEs Muhammad Usama Anjum
2026-09-18 16:03 ` Ryan Roberts
2026-09-18 20:00 ` David Hildenbrand (Arm)
2026-09-21 7:37 ` Ryan Roberts
2026-09-21 8:29 ` Ryan Roberts
2026-09-14 13:51 ` [PATCH 5/6] arm64: use HW PTE accessors in early map_range() Muhammad Usama Anjum
2026-09-21 9:44 ` Ryan Roberts
2026-09-14 13:51 ` [PATCH 6/6] arm64: enable a distinct type for HW PTEs Muhammad Usama Anjum
2026-09-21 9:44 ` Ryan Roberts
2026-09-21 9:51 ` [PATCH 0/6] arm64: distinguish HW PTE pointers from SW PTE value pointers Ryan Roberts
2026-09-21 10:10 ` Muhammad Usama Anjum
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=de9380da-9b3b-4c60-9dfe-45775b3fb889@arm.com \
--to=usama.anjum@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kasan-dev@googlegroups.com \
--cc=liam@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®