From: Mike Rapoport <rppt@kernel.org>
To: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
akpm@linux-foundation.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 0/3] Convert 64-bit x86/mm/pat to ptdescs
Date: Thu, 29 Jan 2026 10:05:16 +0200 [thread overview]
Message-ID: <aXsUvOmmUBEjrjGY@kernel.org> (raw)
In-Reply-To: <20260128224049.385013-1-vishal.moola@gmail.com>
Hi Vishal,
On Wed, Jan 28, 2026 at 02:40:46PM -0800, Vishal Moola (Oracle) wrote:
> x86/mm/pat should be using ptdescs. One line has already been
> converted to pagetable_free(), while the allocation sites use
> get_free_pages(). This causes issues separately allocating ptdescs
> from struct page.
>
> These patches convert the allocation/free sites to use ptdescs. In
> the short term, this helps enable Matthew's work to allocate frozen
> pagetables[1]. And in the long term, this will help us cleanly split
> ptdesc allocations from struct page.
>
> [1] https://lore.kernel.org/linux-mm/20251113140448.1814860-1-willy@infradead.org/
> [2] https://lore.kernel.org/linux-mm/20251020001652.2116669-1-willy@infradead.org/T/#u
>
> ------
>
> I've also tested this on a tree that separately allocates ptdescs. That
> didn't find any lingering alloc/free issues.
>
> I've realized that the pgd_list should also be using ptdescs (for 32bit
> in this file). This can be done in a different patchset since there's
> other users of pgd_list that still need to be converted.
Since Andrew merges cover-letter text into the first commit changelog, some
explanation about pgd_list should be a part of that combined changelog.
> Based on current mm-new.
>
> v2:
> - Use pagetable_alloc() in populate_pgd() - in patch 2
> - Rename subject line to specify 64-bit (i.e. 32-bit wasn't converted)
> - Added reference links to the projects mentioned in the cover letter
>
> Vishal Moola (Oracle) (3):
> x86/mm/pat: Convert pte code to use ptdescs
> x86/mm/pat: Convert pmd code to use ptdescs
> x86/mm/pat: Convert split_large_page() to use ptdescs
>
> arch/x86/mm/pat/set_memory.c | 43 ++++++++++++++++++++----------------
> 1 file changed, 24 insertions(+), 19 deletions(-)
>
> --
> 2.52.0
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-01-29 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 22:40 Vishal Moola (Oracle)
2026-01-28 22:40 ` [PATCH v2 1/3] x86/mm/pat: Convert pte code to use ptdescs Vishal Moola (Oracle)
2026-01-29 8:08 ` Mike Rapoport
2026-01-29 17:04 ` Vishal Moola (Oracle)
2026-01-28 22:40 ` [PATCH v2 2/3] x86/mm/pat: Convert pmd " Vishal Moola (Oracle)
2026-01-28 22:40 ` [PATCH v2 3/3] x86/mm/pat: Convert split_large_page() " Vishal Moola (Oracle)
2026-01-29 8:05 ` Mike Rapoport [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=aXsUvOmmUBEjrjGY@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.org \
--cc=x86@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