From: Miaohe Lin <linmiaohe@huawei.com>
To: Mark Brown <broonie@kernel.org>
Cc: <akpm@linux-foundation.org>, <shuah@kernel.org>,
<david@kernel.org>, <lorenzo.stoakes@oracle.com>,
<Liam.Howlett@oracle.com>, <vbabka@suse.cz>, <rppt@kernel.org>,
<surenb@google.com>, <mhocko@suse.com>, <nao.horiguchi@gmail.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] selftests/mm: add memory failure anonymous page test
Date: Wed, 21 Jan 2026 10:05:07 +0800 [thread overview]
Message-ID: <f1cb6029-9140-3784-5b44-ff58b4edde2c@huawei.com> (raw)
In-Reply-To: <737310eb-05e5-4234-af67-9118b3f395ab@sirena.org.uk>
On 2026/1/21 1:46, Mark Brown wrote:
> On Tue, Jan 20, 2026 at 08:32:37PM +0800, Miaohe Lin wrote:
>
>> +# Try to load hwpoison_inject if not present.
>> +HWPOISON_DIR=/sys/kernel/debug/hwpoison/
>> +if [ ! -d "$HWPOISON_DIR" ]; then
>> + if ! modprobe -q -R hwpoison_inject; then
>> + echo "Module hwpoison_inject not found, skipping..."
>> + else
>> + modprobe hwpoison_inject > /dev/null 2>&1
>> + LOADED_MOD=1
>> + fi
>> +fi
>
> You should also add HWPOISION_INJECT and likely also MEMORY_FAILURE
> (which it depends on) to the config fragment in
>
> tools/testing/selftests/mm/config
Currently if HWPOISION_INJECT or MEMORY_FAILURE isn't enabled, the test
will be skipped.
>
> so people and tools know the config options are needed to get all the
> tests running.
Sounds reasonable. Will add it in next version.
Thanks.
.
next prev parent reply other threads:[~2026-01-21 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:32 [PATCH v2 0/3] selftests/mm: add memory failure selftests Miaohe Lin
2026-01-20 12:32 ` [PATCH v2 1/3] selftests/mm: add memory failure anonymous page test Miaohe Lin
2026-01-20 17:46 ` Mark Brown
2026-01-21 2:05 ` Miaohe Lin [this message]
2026-01-21 11:17 ` Mark Brown
2026-01-21 12:30 ` David Hildenbrand (Red Hat)
2026-01-20 12:32 ` [PATCH v2 2/3] selftests/mm: add memory failure clean pagecache test Miaohe Lin
2026-01-20 12:32 ` [PATCH v2 3/3] selftests/mm: add memory failure dirty " Miaohe Lin
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=f1cb6029-9140-3784-5b44-ff58b4edde2c@huawei.com \
--to=linmiaohe@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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