From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Peter Xu <peterx@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Matthew Wilcox <willy@infradead.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>,
"x86@kernel.org" <x86@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Aneesh Kumar K.V <aneesh.kumar@kernel.org>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
Subject: Re: [PATCH 09/13] mm/powerpc: Redefine pXd_huge() with pXd_leaf()
Date: Thu, 14 Mar 2024 13:11:59 +0000 [thread overview]
Message-ID: <1f6ad500-3ff7-44d4-8223-067bd2ed9ffe@csgroup.eu> (raw)
In-Reply-To: <ZfLzZekFBp3J6JUy@x1n>
Le 14/03/2024 à 13:53, Peter Xu a écrit :
> On Thu, Mar 14, 2024 at 08:45:34AM +0000, Christophe Leroy wrote:
>>
>>
>> Le 13/03/2024 à 22:47, peterx@redhat.com a écrit :
>>> From: Peter Xu <peterx@redhat.com>
>>>
>>> PowerPC book3s 4K mostly has the same definition on both, except pXd_huge()
>>> constantly returns 0 for hash MMUs. As Michael Ellerman pointed out [1],
>>> it is safe to check _PAGE_PTE on hash MMUs, as the bit will never be set so
>>> it will keep returning false.
>>>
>>> As a reference, __p[mu]d_mkhuge() will trigger a BUG_ON trying to create
>>> such huge mappings for 4K hash MMUs. Meanwhile, the major powerpc hugetlb
>>> pgtable walker __find_linux_pte() already used pXd_leaf() to check hugetlb
>>> mappings.
>>>
>>> The goal should be that we will have one API pXd_leaf() to detect all kinds
>>> of huge mappings. AFAICT we need to use the pXd_leaf() impl (rather than
>>> pXd_huge() ones) to make sure ie. THPs on hash MMU will also return true.
>>
>> All kinds of huge mappings ?
>>
>> pXd_leaf() will detect only leaf mappings (like pXd_huge() ). There are
>> also huge mappings through hugepd. On powerpc 8xx we have 8M huge pages
>> and 512k huge pages. A PGD entry covers 4M so pgd_leaf() won't report
>> those huge pages.
>
> Ah yes, I should always mention this is in the context of leaf huge pages
> only. Are the examples you provided all fall into hugepd category? If so
> I can reword the commit message, as:
On powerpc 8xx, only the 8M huge pages fall into the hugepd case.
The 512k hugepages are at PTE level, they are handled more or less like
CONT_PTE on ARM. see function set_huge_pte_at() for more context.
You can also look at pte_leaf_size() and pgd_leaf_size().
By the way pgd_leaf_size() looks odd because it is called only when
pgd_leaf_size() returns true, which never happens for 8M pages.
>
> As a reference, __p[mu]d_mkhuge() will trigger a BUG_ON trying to
> create such huge mappings for 4K hash MMUs. Meanwhile, the major
> powerpc hugetlb pgtable walker __find_linux_pte() already used
> pXd_leaf() to check leaf hugetlb mappings.
>
> The goal should be that we will have one API pXd_leaf() to detect
> all kinds of huge mappings except hugepd. AFAICT we need to use
> the pXd_leaf() impl (rather than pXd_huge() ones) to make sure
> ie. THPs on hash MMU will also return true.
>
> Does this look good to you?
>
> Thanks,
>
next prev parent reply other threads:[~2024-03-14 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 21:47 [PATCH 00/13] mm/treewide: Remove pXd_huge() API peterx
2024-03-13 21:47 ` [PATCH 03/13] mm/gup: Check p4d presence before going on peterx
2024-03-13 21:47 ` [PATCH 06/13] mm/arm: Use macros to define pmd/pud helpers peterx
2024-03-13 21:47 ` [PATCH 07/13] mm/arm: Redefine pmd_huge() with pmd_leaf() peterx
2024-03-13 21:47 ` [PATCH 08/13] mm/arm64: Merge pXd_huge() and pXd_leaf() definitions peterx
2024-03-13 21:47 ` [PATCH 10/13] mm/gup: Merge pXd huge mapping checks peterx
[not found] ` <20240313214719.253873-10-peterx@redhat.com>
2024-03-14 8:45 ` [PATCH 09/13] mm/powerpc: Redefine pXd_huge() with pXd_leaf() Christophe Leroy
[not found] ` <ZfLzZekFBp3J6JUy@x1n>
2024-03-14 13:11 ` Christophe Leroy [this message]
2024-03-18 16:15 ` Jason Gunthorpe
2024-03-19 23:07 ` Christophe Leroy
2024-03-19 23:26 ` Jason Gunthorpe
2024-03-20 6:16 ` Christophe Leroy
[not found] ` <ZfsKIResY4YcxkxK@x1n>
2024-03-20 17:40 ` Christophe Leroy
2024-03-20 20:24 ` Peter Xu
[not found] ` <20240313214719.253873-12-peterx@redhat.com>
2024-03-14 8:50 ` [PATCH 11/13] mm/treewide: Replace " Christophe Leroy
2024-03-14 12:59 ` Peter Xu
2024-03-18 16:16 ` Jason Gunthorpe
[not found] ` <20240313214719.253873-13-peterx@redhat.com>
2024-03-14 8:56 ` [PATCH 12/13] mm/treewide: Remove pXd_huge() Christophe Leroy
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=1f6ad500-3ff7-44d4-8223-067bd2ed9ffe@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=sparclinux@vger.kernel.org \
--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