From: David Hildenbrand <david@redhat.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>, Jann Horn <jannh@google.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@intel.com>,
Alistair Popple <apopple@nvidia.com>,
Peter Zijlstra <peterz@infradead.org>,
Uladzislau Rezki <urezki@gmail.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Andy Lutomirski <luto@kernel.org>, Yi Lai <yi1.lai@intel.com>
Cc: iommu@lists.linux.dev, security@kernel.org, x86@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v5 3/8] x86/mm: Use 'ptdesc' when freeing PMD pages
Date: Thu, 9 Oct 2025 21:25:31 +0200 [thread overview]
Message-ID: <9648e990-18e0-4aed-8110-b02f4b45aa47@redhat.com> (raw)
In-Reply-To: <20250919054007.472493-4-baolu.lu@linux.intel.com>
On 19.09.25 07:40, Lu Baolu wrote:
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> There are a billion ways to refer to a physical memory address.
> One of the x86 PMD freeing code location chooses to use a 'pte_t *' to
> point to a PMD page and then call a PTE-specific freeing function for
> it. That's a bit wonky.
>
> Just use a 'struct ptdesc *' instead. Its entire purpose is to refer
> to page table pages. It also means being able to remove an explicit
> cast.
>
> Right now, pte_free_kernel() is a one-liner that calls
> pagetable_dtor_free(). Effectively, all this patch does is
> remove one superfluous __pa(__va(paddr)) conversion and then
> call pagetable_dtor_free() directly instead of through a helper.
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> ---
> arch/x86/mm/pgtable.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/x86/mm/pgtable.c b/arch/x86/mm/pgtable.c
> index ddf248c3ee7d..2e5ecfdce73c 100644
> --- a/arch/x86/mm/pgtable.c
> +++ b/arch/x86/mm/pgtable.c
> @@ -729,7 +729,7 @@ int pmd_clear_huge(pmd_t *pmd)
> int pud_free_pmd_page(pud_t *pud, unsigned long addr)
> {
> pmd_t *pmd, *pmd_sv;
> - pte_t *pte;
> + struct ptdesc *pt;
> int i;
>
> pmd = pud_pgtable(*pud);
> @@ -750,8 +750,8 @@ int pud_free_pmd_page(pud_t *pud, unsigned long addr)
>
> for (i = 0; i < PTRS_PER_PMD; i++) {
> if (!pmd_none(pmd_sv[i])) {
> - pte = (pte_t *)pmd_page_vaddr(pmd_sv[i]);
> - pte_free_kernel(&init_mm, pte);
> + pt = page_ptdesc(pmd_page(pmd_sv[i]));
> + pagetable_dtor_free(pt);
There is pmd_ptdesc() which does
page_ptdesc(pmd_pgtable_page(pmd));
It's buried in a
#if defined(CONFIG_SPLIT_PMD_PTLOCKS)
Can't we just make that always available so we can use it here?
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-10-09 19:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 5:39 [PATCH v5 0/8] Fix stale IOTLB entries for kernel address space Lu Baolu
2025-09-19 5:39 ` [PATCH v5 1/8] mm: Add a ptdesc flag to mark kernel page tables Lu Baolu
2025-10-08 19:56 ` Matthew Wilcox
2025-10-11 6:24 ` Baolu Lu
2025-09-19 5:40 ` [PATCH v5 2/8] mm: Actually mark kernel page table pages Lu Baolu
2025-10-09 19:19 ` David Hildenbrand
2025-10-13 7:17 ` Mike Rapoport
2025-09-19 5:40 ` [PATCH v5 3/8] x86/mm: Use 'ptdesc' when freeing PMD pages Lu Baolu
2025-10-09 19:25 ` David Hildenbrand [this message]
2025-10-09 19:31 ` Dave Hansen
2025-10-11 6:26 ` Baolu Lu
2025-09-19 5:40 ` [PATCH v5 4/8] mm: Introduce pure page table freeing function Lu Baolu
2025-10-09 19:26 ` David Hildenbrand
2025-10-13 7:24 ` Mike Rapoport
2025-09-19 5:40 ` [PATCH v5 5/8] x86/mm: Use pagetable_free() Lu Baolu
2025-09-24 12:40 ` Jason Gunthorpe
2025-10-09 19:26 ` David Hildenbrand
2025-10-13 7:28 ` Mike Rapoport
2025-09-19 5:40 ` [PATCH v5 6/8] mm: Introduce deferred freeing for kernel page tables Lu Baolu
2025-10-09 19:28 ` David Hildenbrand
2025-10-09 19:32 ` Dave Hansen
2025-10-10 15:47 ` David Hildenbrand
2025-10-11 6:30 ` Baolu Lu
2025-09-19 5:40 ` [PATCH v5 7/8] mm: Hook up Kconfig options for async page table freeing Lu Baolu
2025-09-19 5:40 ` [PATCH v5 8/8] iommu/sva: Invalidate stale IOTLB entries for kernel address space Lu Baolu
2025-09-25 20:24 ` [PATCH v5 0/8] Fix " Dave Hansen
2025-10-08 19:42 ` Dave Hansen
2025-10-09 19:16 ` David Hildenbrand
2025-10-14 13:21 ` Baolu Lu
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=9648e990-18e0-4aed-8110-b02f4b45aa47@redhat.com \
--to=david@redhat.com \
--cc=apopple@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jannh@google.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=robin.murphy@arm.com \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yi1.lai@intel.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