From: sashiko-bot@kernel.org
To: "Muhammad Usama Anjum" <usama.anjum@arm.com>
Cc: linux-perf-users@vger.kernel.org,
intel-gfx@lists.freedesktop.org,
linux-trace-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, damon@lists.linux.dev,
bpf@vger.kernel.org
Subject: Re: [PATCH v3 3/9] mm: use hw_pte_t for generic PTE table storage
Date: Tue, 22 Sep 2026 17:27:12 +0000 [thread overview]
Message-ID: <20260922172712.AD9401F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260922-pte0-v3-3-5670b8cb9059@arm.com>
> Generic page-table interfaces use pte_t * for both pointers to PTE table
> storage and pointers to software PTE values. Convert the generic
> declarations and their MM, fs, and kernel users together so parameters,
> return types, callbacks, and local pointers that designate table storage
> use hw_pte_t *.
>
> Include linux/pgtable_types.h from headers that expose the converted
> interfaces. It continues to provide pgprot_t to vmalloc.h through
> asm/page.h.
>
> Keep software PTE values as pte_t and retain pte_t * for value interfaces.
>
> No architecture selects ARCH_HAS_HW_PTE_T at this point, so hw_pte_t
> remains an alias of pte_t and this changes the interface vocabulary without
> changing representation or behavior.
>
> Most of this mechanical conversion was generated with the Coccinelle script
> included in the cover letter. The script deliberately ignores pte_t *
> pointers named ptentp because they designate software PTE values. The
> result was then audited, and sites the script could not convert were
> updated by hand.
>
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@arm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922-pte0-v3-0-5670b8cb9059@arm.com?part=3
next prev parent reply other threads:[~2026-09-22 17:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 17:12 [PATCH v3 0/9] mm: distinguish HW PTE pointers from SW PTE value pointers Muhammad Usama Anjum
2026-09-22 17:12 ` [PATCH v3 1/9] mm: introduce hw_pte_t for PTE table storage Muhammad Usama Anjum
2026-09-22 17:20 ` sashiko-bot
2026-09-30 4:13 ` Anshuman Khandual
2026-09-30 15:27 ` Zi Yan
2026-09-22 17:12 ` [PATCH v3 2/9] mm: rename pointers to software PTE values as ptentp Muhammad Usama Anjum
2026-09-22 17:21 ` sashiko-bot
2026-09-30 4:20 ` Anshuman Khandual
2026-09-22 17:12 ` [PATCH v3 3/9] mm: use hw_pte_t for generic PTE table storage Muhammad Usama Anjum
2026-09-22 17:27 ` sashiko-bot [this message]
2026-09-30 4:35 ` Anshuman Khandual
2026-09-30 17:40 ` Muhammad Usama Anjum
2026-10-01 11:25 ` David Hildenbrand (Arm)
2026-10-01 11:26 ` David Hildenbrand (Arm)
2026-09-22 17:12 ` [PATCH v3 4/9] mm: convert PTE table entries in ptep_get() Muhammad Usama Anjum
2026-09-22 17:25 ` sashiko-bot
2026-09-30 5:10 ` Anshuman Khandual
2026-09-30 17:46 ` Muhammad Usama Anjum
2026-10-01 11:27 ` David Hildenbrand (Arm)
2026-09-22 17:12 ` [PATCH v3 5/9] mm: convert PTE table entry to pte Muhammad Usama Anjum
2026-09-22 17:19 ` sashiko-bot
2026-10-01 11:17 ` David Hildenbrand (Arm)
2026-10-02 14:57 ` Muhammad Usama Anjum
2026-09-22 17:12 ` [PATCH v3 6/9] mm: add hw_pte_val for HW PTE storage Muhammad Usama Anjum
2026-09-22 17:22 ` sashiko-bot
2026-10-01 11:19 ` David Hildenbrand (Arm)
2026-10-02 14:59 ` Muhammad Usama Anjum
2026-09-22 17:12 ` [PATCH v3 7/9] mm/kasan: use hw_pte_t for the early shadow PTE table Muhammad Usama Anjum
2026-09-22 17:21 ` sashiko-bot
2026-10-01 11:20 ` David Hildenbrand (Arm)
2026-09-22 17:12 ` [PATCH v3 8/9] drm/i915: use hw_pte_t for PTE range callbacks Muhammad Usama Anjum
2026-09-22 17:23 ` sashiko-bot
2026-10-01 11:21 ` David Hildenbrand (Arm)
2026-09-22 17:12 ` [PATCH v3 9/9] xen: " Muhammad Usama Anjum
2026-09-22 17:30 ` sashiko-bot
2026-10-01 11:22 ` David Hildenbrand (Arm)
2026-09-23 23:16 ` ✗ Fi.CI.BUILD: failure for mm: distinguish HW PTE pointers from SW PTE value pointers Patchwork
2026-09-28 7:09 ` [PATCH v3 0/9] " Alexander Gordeev
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=20260922172712.AD9401F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=damon@lists.linux.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=usama.anjum@arm.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