From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Luiz Capitulino <luizcap@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: ryan.roberts@arm.com, akpm@linux-foundation.org,
lorenzo.stoakes@oracle.com
Subject: Re: [RFC 04/10] drivers: i915 selftest: use pgtable_has_pmd_leaves()
Date: Tue, 2 Dec 2025 11:51:00 +0100 [thread overview]
Message-ID: <2149802c-b7cd-430c-8af0-99d26b0b7330@kernel.org> (raw)
In-Reply-To: <21386400-9a67-4fcf-b686-1e7c9678d123@redhat.com>
On 11/17/25 19:55, Luiz Capitulino wrote:
> On 2025-11-17 12:30, David Hildenbrand (Red Hat) wrote:
>> On 06.11.25 22:28, Luiz Capitulino wrote:
>>> igt_can_allocate_thp() uses has_transparente_hugepage() to check if
>>> PMD-sized pages are supported, use pgtable_has_pmd_leaves() instead.
>>>
>>> Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
>>> ---
>>> drivers/gpu/drm/i915/gem/selftests/huge_pages.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/gem/selftests/huge_pages.c b/drivers/gpu/drm/i915/gem/selftests/huge_pages.c
>>> index bd08605a1611..c76aafa36d2b 100644
>>> --- a/drivers/gpu/drm/i915/gem/selftests/huge_pages.c
>>> +++ b/drivers/gpu/drm/i915/gem/selftests/huge_pages.c
>>> @@ -1316,7 +1316,7 @@ typedef struct drm_i915_gem_object *
>>> static inline bool igt_can_allocate_thp(struct drm_i915_private *i915)
>>> {
>>> - return i915->mm.gemfs && has_transparent_hugepage();
>>> + return i915->mm.gemfs && pgtable_has_pmd_leaves();
>>
>> On second thought, is it problematic that we might be losing the CONFIG_TRANSPARENT_HUGEPAGE check? Should we check for that separately?
>
> That's a good point.
>
> In this RFC, pgtable_has_pmd_leaves() should be functionally equivalent
> to has_transparent_hugepage() so I think we're good. That beind said, I
> also think that we should disentangle pgtable_has_pmd_leaves() from THP
> now or in the future. When we do this the breakage you're spotting will
> happen.
>
> What about adding thp_has_pmd_support() which does:
>
> return IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && pgtable_has_pmd_leaves();
>
> Then I can convert all the cases you spotted to thp_has_pmd_support().
I hope we can avoid such a wrapper for the time being. Maybe we can just
keep pgtable_has_pmd_leaves() glued to CONFIG_TRANSPARENT_HUGEPAGE for
now, and leave untangling that for the next cleanup?
--
Cheers
David
next prev parent reply other threads:[~2025-12-02 10:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 21:28 [RFC 00/10] mm: thp: always enable mTHP support Luiz Capitulino
2025-11-06 21:28 ` [RFC 01/10] docs: tmpfs: remove implementation detail reference Luiz Capitulino
2025-11-17 17:26 ` David Hildenbrand (Red Hat)
2025-11-06 21:28 ` [RFC 02/10] mm: introduce pgtable_has_pmd_leaves() Luiz Capitulino
2025-11-06 21:28 ` [RFC 03/10] drivers: dax: use pgtable_has_pmd_leaves() Luiz Capitulino
2025-11-17 17:28 ` David Hildenbrand (Red Hat)
2025-11-06 21:28 ` [RFC 04/10] drivers: i915 selftest: " Luiz Capitulino
2025-11-17 17:29 ` David Hildenbrand (Red Hat)
2025-11-17 17:30 ` David Hildenbrand (Red Hat)
2025-11-17 18:55 ` Luiz Capitulino
2025-12-02 10:51 ` David Hildenbrand (Red Hat) [this message]
2025-12-03 13:19 ` Luiz Capitulino
2025-11-06 21:28 ` [RFC 05/10] drivers: nvdimm: " Luiz Capitulino
2025-11-17 17:32 ` David Hildenbrand (Red Hat)
2025-11-06 21:28 ` [RFC 06/10] mm: debug_vm_pgtable: " Luiz Capitulino
2025-11-17 17:40 ` David Hildenbrand (Red Hat)
2025-12-03 22:09 ` David Hildenbrand (Red Hat)
2025-11-06 21:28 ` [RFC 07/10] treewide: rename has_transparent_hugepage() to arch_has_pmd_leaves() Luiz Capitulino
2025-11-17 17:45 ` David Hildenbrand (Red Hat)
2025-11-17 19:01 ` Luiz Capitulino
2025-12-02 10:53 ` David Hildenbrand (Red Hat)
2025-11-06 21:28 ` [RFC 08/10] mm: replace thp_disabled_by_hw() with pgtable_has_pmd_leaves() Luiz Capitulino
2025-11-06 21:28 ` [RFC 09/10] mm: thp: always enable mTHP support Luiz Capitulino
2025-11-17 17:47 ` David Hildenbrand (Red Hat)
2025-11-17 19:14 ` Luiz Capitulino
2025-11-06 21:28 ` [RFC 10/10] mm: thp: x86: cleanup PSE feature bit usage Luiz Capitulino
2025-11-17 17:49 ` David Hildenbrand (Red Hat)
2025-11-17 19:15 ` Luiz Capitulino
2025-12-03 13:58 ` [RFC 00/10] mm: thp: always enable mTHP support Lorenzo Stoakes
2025-12-03 18:41 ` Luiz Capitulino
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=2149802c-b7cd-430c-8af0-99d26b0b7330@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luizcap@redhat.com \
--cc=ryan.roberts@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