From: Yeoreum Yun <yeoreum.yun@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Yeoreum Yun <yeoreum.yun@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>, Zi Yan <ziy@nvidia.com>,
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 v5 3/3] kselftest: ;, mm: introducealloc_isolated_mem;
Date: Thu, 10 Sep 2026 14:52:07 +0100 [thread overview]
Message-ID: <aqK2B_ehcrcGM-kV@e129823.arm.com> (raw)
In-Reply-To: <8d27168e-5443-4073-bc65-24ddbe32e29a@kernel.org>
On Thu, Sep 10, 2026 at 03:14:36PM +0200, David Hildenbrand (Arm) wrote:
> On 9/10/26 14:34, Yeoreum Yun wrote:
> > On Thu, Sep 10, 2026 at 02:25:40PM +0200, David Hildenbrand (Arm) wrote:
> >> On 9/10/26 14:16, Yeoreum Yun wrote:
> >>>
> >>> True. I overlooked guard bit is sticky.
> >>>
> >>>
> >>> It's enough but alloc_isolated_mem() could be modified to allocate with
> >>> PROT_NONE first and then change the prot.
> >>>
> >>> It seems whether make a helper or testcase should write the code
> >>> properly in case of unwanted VMA merge.
> >>>
> >>> IMHO, instead of testcase write them all
> >>
> >> So far I am aware of exactly one test case, which others do absolutely need this?
> >
> > True. I'll respin with your suggestion.
>
> Don't get me wrong, if we'll need this for other tests we can add helpers. But
> for a single user adding a helper is not really worth it.
No worries. Since I thought there is no use case right now except the
test, I've agreed.
Thanks!
--
Sincerely,
Yeoreum Yun
next prev parent reply other threads:[~2026-09-10 13:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 8:19 [PATCH v5 0/3] kselftest: mm: fix some failure of split_huge_page_test Yeoreum Yun
2026-09-07 8:19 ` [PATCH v5 1/3] kselftest: mm: prevent random failure of huge page split for khugepaged Yeoreum Yun
2026-09-10 10:15 ` David Hildenbrand (Arm)
2026-09-07 8:19 ` [PATCH v5 2/3] kselftest: mm: replace usage of /proc/self/smaps for check_huge_xxx() helper Yeoreum Yun
2026-09-10 10:20 ` David Hildenbrand (Arm)
2026-09-10 10:54 ` Yeoreum Yun
2026-09-10 10:59 ` David Hildenbrand (Arm)
2026-09-10 11:25 ` Yeoreum Yun
2026-09-10 11:27 ` David Hildenbrand (Arm)
2026-09-10 11:31 ` Yeoreum Yun
2026-09-07 8:19 ` [PATCH v5 3/3] kselftest: mm: introduce alloc_isolated_mem() Yeoreum Yun
2026-09-10 10:34 ` David Hildenbrand (Arm)
2026-09-10 11:02 ` Yeoreum Yun
2026-09-10 11:14 ` David Hildenbrand (Arm)
2026-09-10 11:22 ` Yeoreum Yun
2026-09-10 11:24 ` David Hildenbrand (Arm)
2026-09-10 11:30 ` Yeoreum Yun
2026-09-10 11:55 ` David Hildenbrand (Arm)
2026-09-10 12:16 ` Yeoreum Yun
2026-09-10 12:22 ` Yeoreum Yun
2026-09-10 12:25 ` David Hildenbrand (Arm)
2026-09-10 12:34 ` Yeoreum Yun
2026-09-10 13:14 ` David Hildenbrand (Arm)
2026-09-10 13:52 ` Yeoreum Yun [this message]
2026-09-10 10:15 ` [PATCH v5 0/3] kselftest: mm: fix some failure of split_huge_page_test David Hildenbrand (Arm)
2026-09-10 10:31 ` Yeoreum Yun
2026-09-10 10:45 ` David Hildenbrand (Arm)
2026-09-10 11:16 ` Yeoreum Yun
2026-09-10 11:23 ` David Hildenbrand (Arm)
2026-09-10 11:35 ` 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=aqK2B_ehcrcGM-kV@e129823.arm.com \
--to=yeoreum.yun@arm.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=ziy@nvidia.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