From: SJ Park <sj@kernel.org>
Cc: SJ Park <sj@kernel.org>, "Liam R. Howlett" <liam@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@davidgow.net>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
damon@lists.linux.dev, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: [RFC PATCH 00/10] mm/damon: cleanup code, add test cases, and update guidances in docs
Date: Mon, 27 Jul 2026 22:27:59 -0700 [thread overview]
Message-ID: <20260728052811.192712-1-sj@kernel.org> (raw)
Misc cleanup, improvements and updates of code, test, and documents.
Patches 1-3 cleanup DAMON code. Patches 4-8 adds kunit and selftest
test cases for recently fixed bugs and a new feature. Patches 9 and 10
update guidelines for AI review and what document to read, on DAMON
documents.
SJ Park (10):
mm/damon/core: use damon_nr_samples_per_aggr() for max merge threshold
mm/damon/core: remove debug messages
mm/damon/vaddr: remove a debug message
mm/damon/tests/core-kunit: extend set_regions() test for error case
mm/damon/tests/core-kunit: test <=0 size damon_set_regions() inputs
mm/damon/tests/core-kunit: test overlapping ranges for set_regions()
mm/damon/tests/core-kunit: test damon_nr_samples_per_aggr()
selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal
Docs/mm/damon/maintainer-profile: update AI review for Sashiko replies
Docs/ABI/damon: recommend subsystem doc instead of admin-guide
.../ABI/testing/sysfs-kernel-mm-damon | 2 +-
Documentation/mm/damon/maintainer-profile.rst | 19 ++----
mm/damon/core.c | 12 +---
mm/damon/tests/core-kunit.h | 60 ++++++++++++++++---
mm/damon/vaddr.c | 11 +---
tools/testing/selftests/damon/sysfs.sh | 1 +
6 files changed, 61 insertions(+), 44 deletions(-)
base-commit: f5d0a1c210a9bec33ee6cc888f4cc6dd1f56eda7
--
2.47.3
next reply other threads:[~2026-07-28 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 5:27 SJ Park [this message]
2026-07-28 5:28 ` [RFC PATCH 04/10] mm/damon/tests/core-kunit: extend set_regions() test for error case SJ Park
2026-07-28 5:28 ` [RFC PATCH 05/10] mm/damon/tests/core-kunit: test <=0 size damon_set_regions() inputs SJ Park
2026-07-28 5:28 ` [RFC PATCH 06/10] mm/damon/tests/core-kunit: test overlapping ranges for set_regions() SJ Park
2026-07-28 5:28 ` [RFC PATCH 07/10] mm/damon/tests/core-kunit: test damon_nr_samples_per_aggr() SJ Park
2026-07-28 5:28 ` [RFC PATCH 08/10] selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal SJ Park
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=20260728052811.192712-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=davidgow@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.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=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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