From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@davidgow.net>, Shuah Khan <shuah@kernel.org>,
damon@lists.linux.dev, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/6] mm/damon: add kunit and selftests for probes and probe weights
Date: Wed, 2 Sep 2026 07:25:09 -0700 [thread overview]
Message-ID: <20260902142510.87878-1-sj@kernel.org> (raw)
In-Reply-To: <20260902140313.85983-1-sj@kernel.org>
On Wed, 2 Sep 2026 07:03:06 -0700 SJ Park <sj@kernel.org> wrote:
> DAMON recently introduced probes and probe weights. Add kunit and
> selftests for ensuring the parameters for features can be set using the
> core API and the sysfs ABI, respectively.
Sashiko found no blocker for this series. Sashiko sent findings to damon@
mailing list [1], and I replied to all the comments that have any potential
issue finding. Please read those for details.
[1] https://lore.kernel.org/damon/
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-09-02 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 14:03 [PATCH 0/6] mm/damon: add kunit and selftests for probes and probe weights SJ Park
2026-09-02 14:03 ` [PATCH 1/6] mm/damon/tests/core-kunit: test damon_commit_filter() SJ Park
2026-09-02 14:03 ` [PATCH 2/6] mm/damon/tests/core-kunit: add damon_commit_probes() test SJ Park
2026-09-02 14:03 ` [PATCH 3/6] selftests/damon/_damon_sysfs: implement DamonProbes SJ Park
2026-09-02 14:03 ` [PATCH 4/6] selftests/damon/drgn_dump_damon_status: dump probes SJ Park
2026-09-02 14:03 ` [PATCH 5/6] selftests/damon/sysfs.py: extend commit assertion function for probes SJ Park
2026-09-02 14:03 ` [PATCH 6/6] selftests/damon/sysfs.py: test damon probes SJ Park
2026-09-02 14:25 ` SJ Park [this message]
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=20260902142510.87878-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=damon@lists.linux.dev \
--cc=davidgow@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
/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