From: Miaohe Lin <linmiaohe@huawei.com>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: <nao.horiguchi@gmail.com>, <tony.luck@intel.com>,
<wangkefeng.wang@huawei.com>, <willy@infradead.org>,
<akpm@linux-foundation.org>, <osalvador@suse.de>,
<rientjes@google.com>, <duenwen@google.com>,
<jthoughton@google.com>, <jgg@nvidia.com>, <ankita@nvidia.com>,
<peterx@redhat.com>, <sidhartha.kumar@oracle.com>,
<ziy@nvidia.com>, <david@redhat.com>,
<dave.hansen@linux.intel.com>, <muchun.song@linux.dev>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <william.roche@oracle.com>,
<harry.yoo@oracle.com>, <jane.chu@oracle.com>
Subject: Re: [PATCH v3 2/3] selftests/mm: test userspace MFR for HugeTLB hugepage
Date: Mon, 9 Feb 2026 20:01:36 +0800 [thread overview]
Message-ID: <26a7803a-bf20-c60b-459d-2c8f82f2f4f6@huawei.com> (raw)
In-Reply-To: <20260203192352.2674184-3-jiaqiyan@google.com>
On 2026/2/4 3:23, Jiaqi Yan wrote:
> Test the userspace memory failure recovery (MFR) policy for HugeTLB:
>
> 1. Create a memfd backed by HugeTLB and had MFD_MF_KEEP_UE_MAPPED set.
>
> 2. Allocate and map 4 hugepages to the process.
>
> 3. Create sub-threads to MADV_HWPOISON inner addresses of the 1st hugepage.
>
> 4. Check if the process gets correct SIGBUS for each poisoned raw page.
>
> 5. Check if all memory are still accessible and content valid.
>
> 6. Check if the poisoned hugepage is dealt with after memfd released.
>
> Two configurables in the test:
>
> - hugepage_size: size of the hugepage, 1G or 2M.
>
> - nr_hwp_pages: number of pages within the 1st hugepage to MADV_HWPOISON.
>
> Reviewed-by: Jane Chu <jane.chu@oracle.com>
> Signed-off-by: Jiaqi Yan <jiaqiyan@google.com>
It's not required but could this testcase be written into the tools/testing/selftests/mm/memory-failure.c [1]?
[1] https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-unstable&id=cf2929c618fec0a22702b3abd0778bbdde6e458e
Thanks.
.
next prev parent reply other threads:[~2026-02-09 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 19:23 [PATCH v3 0/3] memfd-based Userspace MFR Policy for HugeTLB Jiaqi Yan
2026-02-03 19:23 ` [PATCH v3 1/3] mm: memfd/hugetlb: introduce memfd-based userspace MFR policy Jiaqi Yan
2026-02-04 17:29 ` William Roche
2026-02-10 4:46 ` Jiaqi Yan
2026-02-09 11:54 ` Miaohe Lin
2026-02-10 4:47 ` Jiaqi Yan
2026-02-10 7:31 ` Miaohe Lin
2026-02-13 5:01 ` Jiaqi Yan
2026-02-03 19:23 ` [PATCH v3 2/3] selftests/mm: test userspace MFR for HugeTLB hugepage Jiaqi Yan
2026-02-04 17:53 ` William Roche
2026-02-12 3:11 ` Jiaqi Yan
2026-02-09 12:01 ` Miaohe Lin [this message]
2026-02-12 3:17 ` Jiaqi Yan
2026-02-03 19:23 ` [PATCH v3 3/3] Documentation: add documentation for MFD_MF_KEEP_UE_MAPPED Jiaqi Yan
2026-02-04 17:56 ` William Roche
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=26a7803a-bf20-c60b-459d-2c8f82f2f4f6@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ankita@nvidia.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=duenwen@google.com \
--cc=harry.yoo@oracle.com \
--cc=jane.chu@oracle.com \
--cc=jgg@nvidia.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=rientjes@google.com \
--cc=sidhartha.kumar@oracle.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=william.roche@oracle.com \
--cc=willy@infradead.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