mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zi Yan" <ziy@nvidia.com>
To: "Yeoreum Yun" <yeoreum.yun@arm.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"David Hildenbrand" <david@kernel.org>,
	"Lorenzo Stoakes" <ljs@kernel.org>,
	"Baolin Wang" <baolin.wang@linux.alibaba.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	"Nico Pache" <nico.pache@linux.dev>,
	"Ryan Roberts" <ryan.roberts@arm.com>,
	"Dev Jain" <dev.jain@arm.com>, "Barry Song" <baohua@kernel.org>,
	"Lance Yang" <lance.yang@linux.dev>,
	"Usama Arif" <usama.arif@linux.dev>,
	"Vlastimil Babka" <vbabka@kernel.org>,
	"Mike Rapoport" <rppt@kernel.org>,
	"Suren Baghdasaryan" <surenb@google.com>,
	"Michal Hocko" <mhocko@suse.com>, "Shuah Khan" <shuah@kernel.org>,
	"Kevin Brodsky" <kevin.brodsky@arm.com>, <linux-mm@kvack.org>,
	<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper
Date: Thu, 20 Aug 2026 21:40:29 -0400	[thread overview]
Message-ID: <DKU8M8TD17MK.32V5M766Q1B6B@nvidia.com> (raw)
In-Reply-To: <aoebR7VhQH8kU-xJ@e129823.arm.com>

On Thu Aug 20, 2026 at 8:26 PM EDT, Yeoreum Yun wrote:
> On Thu, Aug 20, 2026 at 08:09:12PM -0400, Zi Yan wrote:
>> On Thu Aug 20, 2026 at 5:26 PM EDT, Yeoreum Yun wrote:
>> >> On Thu Aug 20, 2026 at 3:40 PM EDT, Yeoreum Yun wrote:
>> >> > Since glibc commit 321e1fc73f (“malloc: Enable 2MB THP by default on AArch64”),
>> >> > glibc may call madvise(MADV_HUGEPAGE) for sufficiently large allocations
>> >> > made by memalign().
>> 
>> I just googled the commit and find that Dev did that. ;)
>> 
>> >> >
>> >> > The underlying VMA may start at a different address from the aligned
>> >> > address returned by memalign(). Furthermore, a subsequent
>> >> > madvise(MADV_HUGEPAGE) call does not split the VMA because the flag is
>> >> > already set.
>> >> >
>> >> > This causes split_huge_page_test to fail because the check_huge_xxx()
>> >> > helpers incorrectly require the address returned by memalign() to
>> >> > match the VMA start address reported in /proc/self/smaps.
>> >> >
>> >> > Fix this by using /proc/self/pagemap and /proc/kpageflags instead of
>> >> > /proc/self/smaps to detect huge pages and change the meaning of
>> >> > check_huge_xxx()'s nr_hpages argument:
>> >> 
>> >> Have you checked Baolin's patches[1] in mm-new? They resue
>> >> gather_after_split_folio_orders() to reimplement check_huge_xxx(), also
>> >> based on pagemap and kpageflags. Does it fix the issue?
>> >> 
>> >> [1] https://lore.kernel.org/all/cover.1785985999.git.baolin.wang@linux.alibaba.com/
>> >>
>> >
>> > Unfortunately, No. since __check_pmd_huge() in check_huge_xxx() still use
>> > /proc/self/smaps [1] for pmd THP, it still has problem though ths patch
>> > series applied.
>> >
>> > [1] https://lore.kernel.org/all/56b16691f605426b33b5cf47319233de6127a6b3.1785985999.git.baolin.wang@linux.alibaba.com/
>> 
>> In that case, is it possible to use and extend check_large_folios() for
>> all check_huge_xxx()? You still need pagemap_scan_get_categories() to
>> check PAGE_IS_HUGE to identify huge mappings. Or at least
>> check_huge_xxx() in your patch can share most of the code.
>
> Agree. but TBH, I think check_large_folios() can replace checking
> PAGE_IS_HUGE and keep the later part to check wehther PAGE_IS_FILE

IIUC, PAGE_IS_HUGE comes from checking page table entry (see
pagemap_thp_category()), whereas check_large_folios() checks folios,
namely physical memory. A PTE-mapped order-9 (4KB base page) folio is
!PAGE_IS_HUGE but check_large_folios() returns true for PMD_SIZE.
check_huge_xxx() are checking PMD-mapped folios, so PAGE_IS_HUGE is
functionally equivalent.

> and SWAPBACKED according to check_huge_xxx().
>


-- 
Best Regards,
Yan, Zi


  parent reply	other threads:[~2026-08-21  1:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 19:40 [PATCH 0/2] kselftest: mm: fix some failure of split_huge_page_test Yeoreum Yun
2026-08-20 19:40 ` [PATCH 1/2] kselftest: mm: prevent random failure of huge page split for khugepaged Yeoreum Yun
2026-08-20 19:51   ` Zi Yan
2026-08-20 21:23     ` Yeoreum Yun
2026-08-20 23:37       ` Zi Yan
2026-08-20 23:55         ` Yeoreum Yun
2026-08-21  9:35           ` David Hildenbrand (Arm)
2026-08-20 19:40 ` [PATCH 2/2] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper Yeoreum Yun
2026-08-20 19:55   ` Zi Yan
2026-08-20 21:26     ` Yeoreum Yun
2026-08-21  0:09       ` Zi Yan
2026-08-21  0:26         ` Yeoreum Yun
2026-08-21  1:19           ` Baolin Wang
2026-08-21  1:40           ` Zi Yan [this message]
2026-08-20 23:49   ` Yeoreum Yun

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=DKU8M8TD17MK.32V5M766Q1B6B@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=kevin.brodsky@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=nico.pache@linux.dev \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --cc=yeoreum.yun@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

all inboxes | Powered by JetHome®