From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: sj@kernel.org, honggyu.kim@sk.com
Cc: damon@lists.linux.dev, linux-mm@kvack.org,
Sang-Heon Jeon <ekffu200098@gmail.com>,
Alexandre Ghiti <alexghiti@rivosinc.com>
Subject: [PATCH] selftests/damon: fix selftests by installing drgn related script
Date: Tue, 12 Aug 2025 23:00:46 +0900 [thread overview]
Message-ID: <20250812140046.660486-1-ekffu200098@gmail.com> (raw)
drgn_dump_damon_status is not installed while kselftest setup.
It can breaks other tests which depend on drgn_dump_damon_status.
Install drgn_dump_damon_status files to fix broken test.
Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>
---
While setup kselftest executable environment and test this patch [1],
I found similiar issue. Honestly, I don't know exact solution for this
situation. So I just make a new patch. Sorry if it is wrong direction,
then please let me know how to do next.
[1] https://lore.kernel.org/damon/20250812-alex-fixes_manual-v1-1-c4e99b1f80e4@rivosinc.com/
---
tools/testing/selftests/damon/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/damon/Makefile b/tools/testing/selftests/damon/Makefile
index 44a4a819df55..029de547f31c 100644
--- a/tools/testing/selftests/damon/Makefile
+++ b/tools/testing/selftests/damon/Makefile
@@ -4,6 +4,7 @@
TEST_GEN_FILES += access_memory access_memory_even
TEST_FILES = _damon_sysfs.py
+TEST_FILES += drgn_dump_damon_status.py
# functionality tests
TEST_PROGS += sysfs.sh
--
2.43.0
next reply other threads:[~2025-08-12 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 14:00 Sang-Heon Jeon [this message]
2025-08-12 17:59 ` [PATCH] selftests/damon: fix selftests by installing drgn related script SeongJae Park
2025-08-12 22:17 ` Andrew Morton
2025-08-13 2:29 ` Sang-Heon Jeon
2025-08-13 2:24 ` Sang-Heon Jeon
2025-08-13 2:45 ` SeongJae 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=20250812140046.660486-1-ekffu200098@gmail.com \
--to=ekffu200098@gmail.com \
--cc=alexghiti@rivosinc.com \
--cc=damon@lists.linux.dev \
--cc=honggyu.kim@sk.com \
--cc=linux-mm@kvack.org \
--cc=sj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.