From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v2 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status
Date: Fri, 20 Mar 2026 18:02:00 -0700 [thread overview]
Message-ID: <20260321010201.82092-1-sj@kernel.org> (raw)
In-Reply-To: <20260320154134.99740-1-sj@kernel.org>
On Fri, 20 Mar 2026 08:41:33 -0700 SeongJae Park <sj@kernel.org> wrote:
> On Fri, 20 Mar 2026 08:29:39 -0700 SeongJae Park <sj@kernel.org> wrote:
>
> > Adding Sashiko comment
> > (https://lore.kernel.org/https://sashiko.dev/#/patchset/20260319052157.99433-11-sj@kernel.org)
> > with ': ' line prefix, and my replies in line.
> >
> > On Wed, 18 Mar 2026 22:21:53 -0700 SeongJae Park <sj@kernel.org> wrote:
> >
> > > The sysfs.py test commits DAMON parameters, dump the internal DAMON
> > > state, and show if the parameters are committed as expected using the
> > > dumped state. While the dumping is ongoing, DAMON is alive. It can
> > > make internal changes including addition and removal of regions. It can
> > > therefore make a race that can result in false test results. Pause
> > > DAMON execution during the state dumping to avoid such races.
> > >
> > > Signed-off-by: SeongJae Park <sj@kernel.org>
> > > ---
> > > tools/testing/selftests/damon/sysfs.py | 31 ++++++++++++++++++++++++++
> > > 1 file changed, 31 insertions(+)
> > >
> > > diff --git a/tools/testing/selftests/damon/sysfs.py b/tools/testing/selftests/damon/sysfs.py
> > > index e6d34ba05893f..704729c7a318e 100755
> > > --- a/tools/testing/selftests/damon/sysfs.py
> > > +++ b/tools/testing/selftests/damon/sysfs.py
> > > @@ -193,18 +193,48 @@ def assert_ctx_committed(ctx, dump):
> > > assert_true(dump['pause'] == ctx.pause, 'pause', dump)
> > >
> > > def assert_ctxs_committed(kdamonds):
> > > + ctxs_paused_for_dump = []
> > > + for kd in kdamonds.kdamonds:
> > > + for ctx in kd.contexts:
> > > + if ctx.pause is False:
> > > + ctx.pause = True
> > > + err = kd.commit()
> > > + if err is not None:
> > > + print('pause fail (%s)' % err)
> > > + kdamonds.stop()
> > > + exit(1)
> > > + ctxs_paused_for_dump.append(ctx)
> > > +
> > > status, err = dump_damon_status_dict(kdamonds.kdamonds[0].pid)
> > > if err is not None:
> > > print(err)
> > > kdamonds.stop()
> > > exit(1)
> > >
> > > + for kd in kdamonds.kdamonds:
> > > + for ctx in kd.contexts:
> > > + if ctx in ctxs_paused_for_dump:
> > > + ctx.pause = False
> > > + err = kd.commit()
> > > + if err is not None:
> > > + print('resume fail (%s)' % err)
> > > + kdamonds.stop()
> > > + exit(1)
> > > + # restore for comparison
> > > + ctx.pause = True
> >
> > : If a kdamond contains multiple contexts, does this loop leave earlier contexts
> > : paused in the kernel?
> > :
> > : Since kd.commit() stages and commits the state of all contexts associated with
> > : the kdamond, when kd.commit() is called for the second context, the first
> > : context's local pause attribute is already back to True.
> > :
> > : This would cause kd.commit() to write to sysfs and instruct the kernel to
> > : pause the first context again. By the end of this loop, only the last context
> > : in the kdamond would remain unpaused in the kernel.
> >
> > No. The pause field of the earlier context is set to False, so later
> > kd.commit() will commit the False 'pause' again. But this finds a good point.
> > There is no reason to call kd.commit() for each context. It is more efficient
> > to be called for each kdamond., thouth currently we support only one context
> > per kdamond. I will update the code so, in the next spin.
>
> I'm wrong, Sashiko is correct. I missed the last 'ctx.pause = True' in the
> loop. I will fix this together, like below:
>
> '''
> --- a/tools/testing/selftests/damon/sysfs.py
> +++ b/tools/testing/selftests/damon/sysfs.py
> @@ -201,16 +201,17 @@ def assert_ctx_committed(ctx, dump):
>
> def assert_ctxs_committed(kdamonds):
> ctxs_paused_for_dump = []
> + # pause for safe state dumping
> for kd in kdamonds.kdamonds:
> for ctx in kd.contexts:
> if ctx.pause is False:
> ctx.pause = True
> - err = kd.commit()
> - if err is not None:
> - print('pause fail (%s)' % err)
> - kdamonds.stop()
> - exit(1)
> ctxs_paused_for_dump.append(ctx)
> + err = kd.commit()
> + if err is not None:
> + print('pause fail (%s)' % err)
> + kdamonds.stop()
> + exit(1)
>
> status, err = dump_damon_status_dict(kdamonds.kdamonds[0].pid)
> if err is not None:
> @@ -218,17 +219,19 @@ def assert_ctxs_committed(kdamonds):
> kdamonds.stop()
> exit(1)
>
> + # resume contexts paused for safe state dumping
> for kd in kdamonds.kdamonds:
> - for ctx in kd.contexts:
> - if ctx in ctxs_paused_for_dump:
> - ctx.pause = False
> - err = kd.commit()
> - if err is not None:
> - print('resume fail (%s)' % err)
> - kdamonds.stop()
> - exit(1)
> - # restore for comparison
> - ctx.pause = True
> + for ctx in ctxs_paused_for_dump:
> + ctx.pause = False
> + err = kd.commit()
> + if err is not None:
> + print('resume fail (%s)' % err)
> + kdamonds.stop()
> + exit(1)
> +
> + # restore for comparison
> + for ctx in ctxs_paused_for_dump:
> + ctx.pause = True
>
> ctxs = kdamonds.kdamonds[0].contexts
> dump = status['contexts']
> '''
The above fixup makes the test fails, for the obsolete targets. The fixup
needs another fixup, like below. I will add that to the next spin.
'''
--- a/tools/testing/selftests/damon/sysfs.py
+++ b/tools/testing/selftests/damon/sysfs.py
@@ -200,11 +200,12 @@ def assert_ctxs_committed(kdamonds):
if ctx.pause is False:
ctx.pause = True
ctxs_paused_for_dump.append(ctx)
- err = kd.commit()
- if err is not None:
- print('pause fail (%s)' % err)
- kdamonds.stop()
- exit(1)
+ if len(ctxs_paused_for_dump) > 0:
+ err = kd.commit()
+ if err is not None:
+ print('pause fail (%s)' % err)
+ kdamonds.stop()
+ exit(1)
status, err = dump_damon_status_dict(kdamonds.kdamonds[0].pid)
if err is not None:
@@ -216,11 +217,12 @@ def assert_ctxs_committed(kdamonds):
for kd in kdamonds.kdamonds:
for ctx in ctxs_paused_for_dump:
ctx.pause = False
- err = kd.commit()
- if err is not None:
- print('resume fail (%s)' % err)
- kdamonds.stop()
- exit(1)
+ if len(ctxs_paused_for_dump) > 0:
+ err = kd.commit()
+ if err is not None:
+ print('resume fail (%s)' % err)
+ kdamonds.stop()
+ exit(1)
# restore for comparison
for ctx in ctxs_paused_for_dump:
'''
Thanks,
SJ
prev parent reply other threads:[~2026-03-21 1:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 5:21 [RFC PATCH v2 00/10] mm/damon: let DAMON be paused and resumed SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 01/10] mm/damon/core: introduce damon_ctx->paused SeongJae Park
2026-03-19 6:29 ` SeongJae Park
2026-03-20 15:11 ` SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 02/10] mm/damon/sysfs: add pause file under context dir SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 03/10] Docs/mm/damon/design: update for context pause/resume feature SeongJae Park
2026-03-20 15:17 ` SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 04/10] Docs/admin-guide/mm/damon/usage: update for pause file SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 05/10] Docs/ABI/damon: update for pause sysfs file SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 06/10] mm/damon/tests/core-kunit: test pause commitment SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 07/10] selftests/damon/_damon_sysfs: support pause file staging SeongJae Park
2026-03-20 15:22 ` SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 08/10] selftests/damon/drgn_dump_damon_status: dump pause SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 09/10] selftests/damon/sysfs.py: check pause on assert_ctx_committed() SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status SeongJae Park
2026-03-20 15:29 ` SeongJae Park
2026-03-20 15:41 ` SeongJae Park
2026-03-21 1:02 ` SeongJae 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=20260321010201.82092-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--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 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.