mm/damon: let DAMON be paused and resumed
Subsystems (5)
SeongJae Park
maintainerv2 cover mm/damon: let DAMON be paused and resumed
DAMON utilizes a few mechanisms that enhance itself over time. Adaptive regions adjustment, goal-based DAMOS quota auto-tuning and monitoring intervals auto-tuning like self-training mechanisms are such examples. It also adds access frequency stability information (age) to the monitoring results, which makes it enhanced over time.
Sometimes users have to stop DAMON. In this case, DAMON internal state that enhanced over the time of the last execution simply goes away. Restarted DAMON have to train itself and enhance its output from the scratch. This makes DAMON less useful in such cases. Introducing three such use cases below.
Investigation of DAMON. It is best to do the investigation online, especially when it is a production environment. DAMON therefore provides features for such online investigations, including DAMOS stats, monitoring result snapshot exposure, and multiple tracepoints. When those are insufficient, and there are additional clues that could be interfered by DAMON, users have to temporarily stop DAMON to collect the additional clues. It is not very useful since many of DAMON internal clues are gone when DAMON is stopped. The loss of the monitoring results that improved over time is also problematic, especially in production environments.
Monitoring of workloads that have different user-known phases. For example, in Android, applications are known to have very different access patterns and behaviors when they are running on the foreground and the background. It can therefore be useful to separate monitoring of apps based on whether they are running on the foreground and on the background. Having two DAMON threads per application that paused and resumed for the apps foreground/background switches can be useful for the purpose. But such pause/resume of the execution is not supported.
Tests of DAMON. A few DAMON selftests are using drgn to dump the internal DAMON status. The tests show if the dumped status is the same as what the test code expected. Because DAMON keeps running and modifying its internal status, there are chances of data races that can cause false test results. Stopping DAMON can avoid the race. But, since the internal state of DAMON is dropped, the test coverage will be limited.
Let DAMON execution be paused and resumed without loss of the internal state, to overhaul the limitations. For this, introduce a new DAMON context parameter, namely 'pause'. API callers can update it while the context is running, using the online parameters update functions (damon_commit_ctx() and damon_call()). Once it is set, kdamond_fn() main loop will do only limited works excluding the monitoring and DAMOS works, while sleeping sampling intervals per the work. The limited works include handling of the online parameters update. Hence users can unset the 'pause' parameter again. Once it is unset, kdamond_fn() main loop will do all the work again (resumed). Under the paused state, it also does stop condition checks and handling of it, so that paused DAMON can also be stopped if needed. Expose the feature to the user space via DAMON sysfs interface. Also, update existing drgn-based tests to test and use the feature.
Tests
=====
I confirmed the feature functionality using real time tracing ('perf trace' or 'trace-cmd stream') of damon:damon_aggregated DAMON tracepoint. By pausing and resuming the DAMON execution, I was able to see the trace stops and continued as expected. Note that the pause feature support is added to DAMON user-space tool (damo) after v3.1.9. Users can use '--pause_ctx' command line option of damo for that, and I actually used it for my test. The extended drgn-based selftests are also testing a part of the functionality.
Patches Sequence
================
Patch 1 introduces the new core API for the pause feature. Patch 2 extend DAMON sysfs interface for the new parameter. Patches 3-5 update design, usage and ABI documents for the new sysfs file, respectively. The following five patches are for tests. Patch 6 implements a new kunit test for the pause parameter online commitment. Patches 7 and 8 extend DAMON selftest helpers to support the new feature. Patch 9 extends selftest to test the commitment of the feature. Finally, patch 10 updates existing selftest to be safe from the race condition using the pause/resume feature.
Changelog
=========
Changes from RFC v1
(https://lore.kernel.org/[email protected])
- Continuously cancel new damos_walk() requests when paused.
- Initialize damon_sysfs_context->pause.
- Make sysfs.py dump-purpose pausing to work for all contexts.
SeongJae Park (10):
mm/damon/core: introduce damon_ctx->paused mm/damon/sysfs: add pause file under context dir Docs/mm/damon/design: update for context pause/resume feature Docs/admin-guide/mm/damon/usage: update for pause file Docs/ABI/damon: update for pause sysfs file mm/damon/tests/core-kunit: test pause commitment selftests/damon/_damon_sysfs: support pause file staging selftests/damon/drgn_dump_damon_status: dump pause selftests/damon/sysfs.py: check pause on assert_ctx_committed() selftets/damon/sysfs.py: pause DAMON before dumping status
.../ABI/testing/sysfs-kernel-mm-damon | 7 ++++ Documentation/admin-guide/mm/damon/usage.rst | 12 ++++--- Documentation/mm/damon/design.rst | 7 ++++ include/linux/damon.h | 2 ++ mm/damon/core.c | 9 ++++++ mm/damon/sysfs.c | 31 ++++++++++++++++++ mm/damon/tests/core-kunit.h | 4 +++ tools/testing/selftests/damon/_damon_sysfs.py | 10 +++++- .../selftests/damon/drgn_dump_damon_status.py | 1 + tools/testing/selftests/damon/sysfs.py | 32 +++++++++++++++++++ 10 files changed, 110 insertions(+), 5 deletions(-)
base-commit: 89fea69e3a636d7f4c7a0dee9c25e2b417a74c7a
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 1/10 mm/damon/core: introduce damon_ctx->paused
DAMON supports only start and stop of the execution. When it is stopped, its internal data that it self-trained goes away. It will be useful if the execution can be paused and resumed with the previous self-trained data.
Introduce per-context API parameter, 'paused', for the purpose. The parameter can be set and unset while DAMON is running and paused, using the online parameters commit helper functions (damon_commit_ctx() and damon_call()). Once 'paused' is set, the kdamond_fn() main loop does only limited works with sampling interval sleep during the works. The limited works include the handling of the online parameters update, so that users can unset the 'pause' and resume the execution when they want. It also keep checking DAMON stop conditions and handling of it, so that DAMON can be stopped while paused if needed.
--- include/linux/damon.h | 2 ++ mm/damon/core.c | 9 +++++++++ 2 files changed, 11 insertions(+)
include/linux/damon.h +2 -0
@@ -811,6 +811,8 @@ struct damon_ctx {* intervals tuning */ unsigned long next_intervals_tune_sis; +/* pause kdamond main loop */ +bool pause;/* for waiting until the execution of the kdamond_fn is started */ struct completion kdamond_started;/* for scheme quotas prioritization */
mm/damon/core.c +9 -0
@@ -1331,6 +1331,7 @@ int damon_commit_ctx(struct damon_ctx *dst, struct damon_ctx *src)if (err)return err; } + dst->pause = src->pause; dst->ops = src->ops; dst->addr_unit = src->addr_unit; dst->min_region_sz = src->min_region_sz;
@@ -2978,6 +2979,14 @@ static int kdamond_fn(void *data)* kdamond_merge_regions() if possible, to reduce overhead */ kdamond_call (ctx, false); +while (ctx->pause) { +if (kdamond_need_stop (ctx)) + goto done; +kdamond_usleep (ctx->attrs.sample_interval); +/* allow caller unset pause via damon_call() */ +kdamond_call (ctx, false); +damos_walk_cancel (ctx); + }if (!list_empty (&ctx->schemes))kdamond_apply_schemes (ctx);else
Signature · 1 line
2.47.3
SeongJae Park
maintainerRe: [RFC PATCH v2 01/10] mm/damon/core: introduce damon_ctx->paused
Quoted 26 lines · On Wed, 18 Mar 2026 22:21:44 -0700 SeongJae Park <[email protected]> wrote:
DAMON supports only start and stop of the execution. When it is stopped, its internal data that it self-trained goes away. It will be useful if the execution can be paused and resumed with the previous self-trained data.
Introduce per-context API parameter, 'paused', for the purpose. The parameter can be set and unset while DAMON is running and paused, using the online parameters commit helper functions (
damon_commit_ctx()anddamon_call()). Once 'paused' is set, thekdamond_fn()main loop does only limited works with sampling interval sleep during the works. The limited works include the handling of the online parameters update, so that users can unset the 'pause' and resume the execution when they want. It also keep checking DAMON stop conditions and handling of it, so that DAMON can be stopped while paused if needed.Signed-off-by SeongJae Park <[email protected]>--- include/linux/damon.h | 2 ++ mm/damon/core.c | 9 +++++++++ 2 files changed, 11 insertions(+)include/linux/damon.h +0
-0
include/linux/damon.h struct damon_ctx { · line 815
Quoted 5 lines
include/linux/damon.h +2
-0@@ -811,6 +811,8 @@ struct damon_ctx {* intervals tuning */ unsigned long next_intervals_tune_sis; +/* pause kdamond main loop */ +bool pause;
This field will be directly set by an API caller. But this diff is defining this field in the private fields section. I will change this to be defined in the public fields section, and add the kernel-doc comment, in the next version.
Thanks,
SJ
[...]
SeongJae Park
maintainerRe: [RFC PATCH v2 01/10] mm/damon/core: introduce damon_ctx->paused
In reply to SeongJae ParkQuoted 47 lines · On Wed, 18 Mar 2026 22:21:44 -0700 SeongJae Park <[email protected]> wrote:
DAMON supports only start and stop of the execution. When it is stopped, its internal data that it self-trained goes away. It will be useful if the execution can be paused and resumed with the previous self-trained data.
Introduce per-context API parameter, 'paused', for the purpose. The parameter can be set and unset while DAMON is running and paused, using the online parameters commit helper functions (
damon_commit_ctx()anddamon_call()). Once 'paused' is set, thekdamond_fn()main loop does only limited works with sampling interval sleep during the works. The limited works include the handling of the online parameters update, so that users can unset the 'pause' and resume the execution when they want. It also keep checking DAMON stop conditions and handling of it, so that DAMON can be stopped while paused if needed.Signed-off-by SeongJae Park <[email protected]>--- include/linux/damon.h | 2 ++ mm/damon/core.c | 9 +++++++++ 2 files changed, 11 insertions(+)include/linux/damon.h +2
-0@@ -811,6 +811,8 @@ struct damon_ctx {* intervals tuning */ unsigned long next_intervals_tune_sis; +/* pause kdamond main loop */ +bool pause;/* for waiting until the execution of the kdamond_fn is started */ struct completion kdamond_started;/* for scheme quotas prioritization */ mm/damon/core.c +1
-0@@ -1331,6 +1331,7 @@ int damon_commit_ctx(struct damon_ctx *dst, struct damon_ctx *src)if (err)return err; } + dst->pause = src->pause; dst->ops = src->ops; dst->addr_unit = src->addr_unit; dst->min_region_sz = src->min_region_sz;
mm/damon/core.c static int kdamond_fn(void *data) · line 2988
Quoted 10 lines
mm/damon/core.c +7
-0@@ -2978,6 +2979,14 @@ static int kdamond_fn(void *data)* kdamond_merge_regions() if possible, to reduce overhead */ kdamond_call (ctx, false); +while (ctx->pause) { +if (kdamond_need_stop (ctx)) + goto done; +kdamond_usleep (ctx->attrs.sample_interval); +/* allow caller unset pause via damon_call() */ +kdamond_call (ctx, false); +damos_walk_cancel (ctx);
Sashiko comment
(https://sashiko.dev/#/patchset/[email protected]) and my reply below.
: Can this cause spurious cancellations of DAMOS walk requests if the context : is unpaused?
:
: If kdamond_call() processes a commit that sets ctx->pause = false, and a new : walk request is queued concurrently or immediately after, this unconditional : call to damos_walk_cancel() will cancel the newly submitted request before : the loop condition is evaluated again to exit the loop.
:
: Would it be safer to verify if the context is still paused before cancelling, : perhaps by checking if (ctx->pause) before calling damos_walk_cancel()?
Yes, it can cause unnecessary cancel of damos_walk() request. But cancelling a few more damos_walk() request is no big deal. The caller and user can show it is cancelled, and just ask it again.
So, not a problem.
Thanks,
SJ
[...]
SeongJae Park
maintainerRFC PATCH v2 2/10 mm/damon/sysfs: add pause file under context dir
In reply to SeongJae ParkAdd pause DAMON sysfs file under the context directory. It exposes the damon_ctx->pause API parameter to the users so that they can use the pause/resume feature.
--- mm/damon/sysfs.c | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+)
mm/damon/sysfs.c +31 -0
@@ -866,6 +866,7 @@ struct damon_sysfs_context {struct damon_sysfs_attrs *attrs;struct damon_sysfs_targets *targets;struct damon_sysfs_schemes *schemes; +bool pause; }; static struct damon_sysfs_context *damon_sysfs_context_alloc(
@@ -878,6 +879,7 @@ static struct damon_sysfs_context *damon_sysfs_context_alloc( context->kobj = (struct kobject ){}; context->ops_id = ops_id; context->addr_unit =1 ; + context->pause = false;return context; }
@@ -1053,6 +1055,30 @@ static ssize_t addr_unit_store(struct kobject *kobj,return count; } +static ssize_t pause_show (struct kobject *kobj,struct kobj_attribute *attr, +char *buf) +{ +struct damon_sysfs_context *context =container_of (kobj, + struct damon_sysfs_context, kobj); + +return sysfs_emit (buf,"%c\n" , context->pause ?'Y' :'N' ); +} + +static ssize_t pause_store (struct kobject *kobj,struct kobj_attribute *attr, +const char *buf,size_t count) +{ +struct damon_sysfs_context *context =container_of (kobj, + struct damon_sysfs_context, kobj); +bool pause; +int err =kstrtobool (buf, &pause); + +if (err) +return err; + context->pause = pause; +return count; +} + +static void damon_sysfs_context_release (struct kobject *kobj) {kfree (container_of(kobj ,struct damon_sysfs_context ,kobj ));
@@ -1067,10 +1093,14 @@ static struct kobj_attribute damon_sysfs_context_operations_attr =static struct kobj_attribute damon_sysfs_context_addr_unit_attr =__ATTR_RW_MODE (addr_unit,0600 ); +static struct kobj_attribute damon_sysfs_context_pause_attr = +__ATTR_RW_MODE (pause,0600 ); +static struct attribute *damon_sysfs_context_attrs[] = { &damon_sysfs_context_avail_operations_attr.attr, &damon_sysfs_context_operations_attr.attr, &damon_sysfs_context_addr_unit_attr.attr, + &damon_sysfs_context_pause_attr.attr,NULL , };ATTRIBUTE_GROUPS (damon_sysfs_context);
@@ -1470,6 +1500,7 @@ static int damon_sysfs_apply_inputs(struct damon_ctx *ctx,if (sys_ctx->ops_id ==DAMON_OPS_PADDR ) ctx->min_region_sz =max (DAMON_MIN_REGION_SZ / sys_ctx->addr_unit,1 ); + ctx->pause = sys_ctx->pause; err =damon_sysfs_set_attrs (ctx, sys_ctx->attrs);if (err)return err;
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 3/10 Docs/mm/damon/design: update for context pause/resume feature
In reply to SeongJae ParkUpdate DAMON design document for the context execution pause/resume feature.
--- Documentation/mm/damon/design.rst | 7 +++++++ 1 file changed, 7 insertions(+)
Documentation/mm/damon/design.rst +7 -0
@@ -19,6 +19,13 @@ types of monitoring. To know how user-space can do the configurations and start/stop DAMON, refer to :ref:`DAMON sysfs interface <sysfs_interface>` documentation. +Users can also request each context execution to be paused and resumed. When +it is paused, the kdamond does nothing but only online parameters updates +including resume request handling. + +To know how user-space can pause/resume each context, refer to :ref:`DAMON +sysfs context <sysfs_context>` usage documentation. + Overall Architecture ====================
Signature · 1 line
2.47.3
SeongJae Park
maintainerRe: [RFC PATCH v2 03/10] Docs/mm/damon/design: update for context pause/resume feature
Quoted 13 lines · On Wed, 18 Mar 2026 22:21:46 -0700 SeongJae Park <[email protected]> wrote:
Update DAMON design document for the context execution pause/resume feature.
Signed-off-by SeongJae Park <[email protected]>--- Documentation/mm/damon/design.rst | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/mm/damon/design.rst +0
-0
Documentation/mm/damon/design.rst types of monitoring. · line 24
Quoted 6 lines
Documentation/mm/damon/design.rst +3
-0@@ -19,6 +19,13 @@ types of monitoring. To know how user-space can do the configurations and start/stop DAMON, refer to :ref:`DAMON sysfs interface <sysfs_interface>` documentation. +Users can also request each context execution to be paused and resumed. When +it is paused, the kdamond does nothing but only online parameters updates +including resume request handling.
Sashiko comment
(https://sashiko.dev/#/patchset/[email protected]) below.
: This isn't a bug, but the phrasing "does nothing but only online parameters : updates" is a bit awkward. Could this be reworded for clarity, perhaps to : something like "does nothing other than apply online parameter updates"?
I pretty sure Sashiko is more English fluent than I. But, shouldn't 's/apply/applying/' ? I will update the sentence to "When it is paused, the kdamond does nothing other than applying online parameter update" in the next revision.
Thanks,
SJ
[...]
SeongJae Park
maintainerRFC PATCH v2 4/10 Docs/admin-guide/mm/damon/usage: update for pause file
In reply to SeongJae ParkUpdate DAMON usage document for the DAMON context execution pause/resume feature.
--- Documentation/admin-guide/mm/damon/usage.rst | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
Documentation/admin-guide/mm/damon/usage.rst +8 -4
@@ -66,7 +66,8 @@ comma (","). │ :ref:`kdamonds <sysfs_kdamonds>`/nr_kdamonds │ │ :ref:`0 <sysfs_kdamond>`/state,pid,refresh_ms │ │ │ :ref:`contexts <sysfs_contexts>`/nr_contexts - │ │ │ │ :ref:`0 <sysfs_context>`/avail_operations,operations,addr_unit + │ │ │ │ :ref:`0 <sysfs_context>`/avail_operations,operations,addr_unit, + │ │ │ │ pause │ │ │ │ │ :ref:`monitoring_attrs <sysfs_monitoring_attrs>`/ │ │ │ │ │ │ intervals/sample_us,aggr_us,update_us │ │ │ │ │ │ │ intervals_goal/access_bp,aggrs,min_sample_us,max_sample_us
@@ -194,9 +195,9 @@ details). At the moment, only one context per kdamond is supported, so only contexts/<N>/ ------------- -In each context directory, three files (``avail_operations``, ``operations`` -and ``addr_unit``) and three directories (``monitoring_attrs``, ``targets``, -and ``schemes``) exist. +In each context directory, four files (``avail_operations``, ``operations``, +``addr_unit`` and ``pause``) and three directories (``monitoring_attrs``, +``targets``, and ``schemes``) exist. DAMON supports multiple types of :ref:`monitoring operations <damon_design_configurable_operations_set>`, including those for virtual address
@@ -214,6 +215,9 @@ reading from the ``operations`` file. ``addr_unit`` file is for setting and getting the :ref:`address unit <damon_design_addr_unit>` parameter of the operations set. +``pause`` file is for setting and getting the :ref:`pause request +<damon_design_execution_model_and_data_structures>` parameter of the context. + .. _sysfs_monitoring_attrs: contexts/<N>/monitoring_attrs/
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 5/10 Docs/ABI/damon: update for pause sysfs file
In reply to SeongJae ParkUpdate DAMON ABI document for the DAMON context execution pause/resume feature.
--- Documentation/ABI/testing/sysfs-kernel-mm-damon | 7 +++++++ 1 file changed, 7 insertions(+)
Documentation/ABI/testing/sysfs-kernel-mm-damon +7 -0
@@ -84,6 +84,13 @@ Description: Writing an integer to this file sets the 'address unit' parameter of the given operations set of the context. Reading the file returns the last-written 'address unit' value. +What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/pause +Date: Mar 2026 +Contact: SeongJae Park <[email protected]> +Description: Writing a boolean keyword to this file sets the 'pause' request + parameter for the context. Reading the file returns the + last-written 'pause' value. + What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/monitoring_attrs/intervals/sample_us Date: Mar 2022 Contact: SeongJae Park <[email protected]>
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 6/10 mm/damon/tests/core-kunit: test pause commitment
In reply to SeongJae ParkAdd a kunit test for commitment of damon_ctx->pause parameter that can be done using damon_commit_ctx().
--- mm/damon/tests/core-kunit.h | 4 ++++ 1 file changed, 4 insertions(+)
mm/damon/tests/core-kunit.h +4 -0
@@ -1077,6 +1077,10 @@ static void damon_test_commit_ctx(struct kunit *test)KUNIT_EXPECT_EQ (test,damon_commit_ctx (dst, src),0 ); src->min_region_sz =4095 ;KUNIT_EXPECT_EQ (test,damon_commit_ctx (dst, src), -EINVAL ); + src->min_region_sz =4096 ; + src->pause = true; +KUNIT_EXPECT_EQ (test,damon_commit_ctx (dst, src),0 ); +KUNIT_EXPECT_TRUE (test, dst->pause);damon_destroy_ctx (src);damon_destroy_ctx (dst); }
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 7/10 selftests/damon/_damon_sysfs: support pause file staging
In reply to SeongJae ParkDAMON test-purpose sysfs interface control Python module, _damon_sysfs, is not supporting the newly added pause file. Add the support of the file, for future test and use of the feature.
--- tools/testing/selftests/damon/_damon_sysfs.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
tools/testing/selftests/damon/_damon_sysfs.py +9 -1
@@ -604,10 +604,11 @@ class DamonCtx: targets = None schemes = None kdamond = None + pause = None idx = None def __init__(self, ops='paddr', monitoring_attrs=DamonAttrs(), targets=[], - schemes=[]): + schemes=[], pause=False): self.ops = ops self.monitoring_attrs = monitoring_attrs self.monitoring_attrs.context = self
@@ -622,6 +623,8 @@ class DamonCtx: scheme.idx = idx scheme.context = self + self.pause=pause + def sysfs_dir(self): return os.path.join(self.kdamond.sysfs_dir(), 'contexts', '%d' % self.idx)
@@ -662,6 +665,11 @@ class DamonCtx: err = scheme.stage() if err is not None: return err + + err = write_file(os.path.join(self.sysfs_dir(), 'pause'), self.pause) + if err is not None: + return err + return None class Kdamond:
Signature · 1 line
2.47.3
SeongJae Park
maintainerRe: [RFC PATCH v2 07/10] selftests/damon/_damon_sysfs: support pause file staging
Quoted 14 lines · On Wed, 18 Mar 2026 22:21:50 -0700 SeongJae Park <[email protected]> wrote:
DAMON test-purpose sysfs interface control Python module,
_damon_sysfs, is not supporting the newly added pause file. Add the support of the file, for future test and use of the feature.Signed-off-by SeongJae Park <[email protected]>--- tools/testing/selftests/damon/_damon_sysfs.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)tools/testing/selftests/damon/_damon_sysfs.py +0
-0
tools/testing/selftests/damon/_damon_sysfs.py class DamonCtx: · line 611
Quoted 9 lines
tools/testing/selftests/damon/_damon_sysfs.py +2
-1@@ -604,10 +604,11 @@ class DamonCtx: targets = None schemes = None kdamond = None + pause = None idx = None def __init__(self, ops='paddr', monitoring_attrs=DamonAttrs(), targets=[], - schemes=[]): + schemes=[], pause=False):
Sashiko comment
(https://sashiko.dev/#/patchset/[email protected]) and my reply.
: Since this line is being modified, could the use of mutable default : arguments for monitoring_attrs, targets, and schemes cause unintended : state sharing between instances?
:
: In Python, default arguments are evaluated exactly once at function : definition time. If multiple DamonCtx objects are instantiated without : explicitly providing these parameters, they will share the exact same : object instances in memory.
:
: When the constructor later executes self.monitoring_attrs.context = self, : it overwrites the context reference of the shared object to point to the : newest DamonCtx instance. If multiple contexts are staged concurrently : relying on the default arguments, earlier contexts might inadvertently : write their sysfs files into the directory of the last created context. :
: Would it be better to use None for the defaults and instantiate new objects : inside the constructor?
Good points. Orthogonal to this patch, though. Also, there is no such use case of this class to my best knowledge. I will consider such change later, though.
Thanks,
SJ
[...]
SeongJae Park
maintainerRFC PATCH v2 8/10 selftests/damon/drgn_dump_damon_status: dump pause
In reply to SeongJae Parkdrgn_dump_damon_status is not dumping the damon_ctx->pause parameter value, so it cannot be tested. Dump it for future tests.
--- tools/testing/selftests/damon/drgn_dump_damon_status.py | 1 + 1 file changed, 1 insertion(+)
tools/testing/selftests/damon/drgn_dump_damon_status.py +1 -0
@@ -200,6 +200,7 @@ def damon_ctx_to_dict(ctx): ['attrs', attrs_to_dict], ['adaptive_targets', targets_to_list], ['schemes', schemes_to_list], + ['pause', bool], ]) def main():
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 9/10 selftests/damon/sysfs.py: check pause on assert_ctx_committed()
In reply to SeongJae ParkExtend sysfs.py tests to confirm damon_ctx->pause can be set using the pause sysfs file.
--- tools/testing/selftests/damon/sysfs.py | 1 + 1 file changed, 1 insertion(+)
tools/testing/selftests/damon/sysfs.py +1 -0
@@ -190,6 +190,7 @@ def assert_ctx_committed(ctx, dump): assert_monitoring_attrs_committed(ctx.monitoring_attrs, dump['attrs']) assert_monitoring_targets_committed(ctx.targets, dump['adaptive_targets']) assert_schemes_committed(ctx.schemes, dump['schemes']) + assert_true(dump['pause'] == ctx.pause, 'pause', dump) def assert_ctxs_committed(kdamonds): status, err = dump_damon_status_dict(kdamonds.kdamonds[0].pid)
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH v2 10/10 selftets/damon/sysfs.py: pause DAMON before dumping status
In reply to SeongJae ParkThe 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.
--- tools/testing/selftests/damon/sysfs.py | 31 ++++++++++++++++++++++++++ 1 file changed, 31 insertions(+)
tools/testing/selftests/damon/sysfs.py +31 -0
@@ -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 + ctxs = kdamonds.kdamonds[0].contexts dump = status['contexts'] assert_true(len(ctxs) == len(dump), 'ctxs length', dump) for idx, ctx in enumerate(ctxs): assert_ctx_committed(ctx, dump[idx]) + # restore for the caller + for kd in kdamonds.kdamonds: + for ctx in kd.contexts: + if ctx in ctxs_paused_for_dump: + ctx.pause = False + def main(): kdamonds = _damon_sysfs.Kdamonds( [_damon_sysfs.Kdamond(
@@ -302,6 +332,7 @@ def main(): print('kdamond start failed: %s' % err) exit(1) kdamonds.kdamonds[0].contexts[0].targets[1].obsolete = True + kdamonds.kdamonds[0].contexts[0].pause = True kdamonds.kdamonds[0].commit() del kdamonds.kdamonds[0].contexts[0].targets[1] assert_ctxs_committed(kdamonds)
Signature · 1 line
2.47.3
SeongJae Park
maintainerRe: [RFC PATCH v2 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status
Adding Sashiko comment
(https://lore.kernel.org/https://sashiko.dev/#/patchset/[email protected])
with ': ' line prefix, and my replies in line.
Quoted 39 lines · On Wed, 18 Mar 2026 22:21:53 -0700 SeongJae Park <[email protected]> wrote:
The
sysfs.pytest 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 <[email protected]>--- tools/testing/selftests/damon/sysfs.py | 31 ++++++++++++++++++++++++++ 1 file changed, 31 insertions(+)tools/testing/selftests/damon/sysfs.py +13
-0@@ -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:
tools/testing/selftests/damon/sysfs.py def assert_ctx_committed(ctx, dump): · line 224
Quoted 10 lines
tools/testing/selftests/damon/sysfs.py +10
-0+ 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.
tools/testing/selftests/damon/sysfs.py def assert_ctx_committed(ctx, dump): · line 236
Quoted 12 lines
tools/testing/selftests/damon/sysfs.py +6
-0+ ctxs = kdamonds.kdamonds[0].contexts dump = status['contexts'] assert_true(len(ctxs) == len(dump), 'ctxs length', dump) for idx, ctx in enumerate(ctxs): assert_ctx_committed(ctx, dump[idx]) + # restore for the caller + for kd in kdamonds.kdamonds: + for ctx in kd.contexts: + if ctx in ctxs_paused_for_dump: + ctx.pause = False
: Since kd.commit() is not called after restoring the Python objects here, does : this leave the previous contexts permanently paused in the kernel while their : Python state reflects them as running?
No, we already unpaused the unpause-required contexts above.
Thanks,
SJ
[...]
SeongJae Park
maintainerRe: [RFC PATCH v2 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status
Quoted 67 lines · On Fri, 20 Mar 2026 08:29:39 -0700 SeongJae Park <[email protected]> wrote:
Adding Sashiko comment
(https://lore.kernel.org/https://sashiko.dev/#/patchset/[email protected])
with ': ' line prefix, and my replies in line.Quoted 39 lines · On Wed, 18 Mar 2026 22:21:53 -0700 SeongJae Park <[email protected]> wrote:
The
sysfs.pytest 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 <[email protected]>--- tools/testing/selftests/damon/sysfs.py | 31 ++++++++++++++++++++++++++ 1 file changed, 31 insertions(+)tools/testing/selftests/damon/sysfs.py +13
-0@@ -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:tools/testing/selftests/damon/sysfs.py def assert_ctx_committed(ctx, dump): · line 224
Quoted 10 lines
tools/testing/selftests/damon/sysfs.py +10
-0+ 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?
:
: Sincekd.commit()stages and commits the state of all contexts associated with : the kdamond, whenkd.commit()is called for the second context, the first : context's local pause attribute is already back to True.
:
: This would causekd.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.
Quoted 5 lines
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 callkd.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:
'''
tools/testing/selftests/damon/sysfs.py +18 -15
@@ -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']
'''
Thanks,
SJ
[...]
SeongJae Park
maintainerRe: [RFC PATCH v2 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status
Quoted 134 lines · On Fri, 20 Mar 2026 08:41:33 -0700 SeongJae Park <[email protected]> wrote:
Quoted 67 lines · On Fri, 20 Mar 2026 08:29:39 -0700 SeongJae Park <[email protected]> wrote:
Adding Sashiko comment
(https://lore.kernel.org/https://sashiko.dev/#/patchset/[email protected])
with ': ' line prefix, and my replies in line.Quoted 39 lines · On Wed, 18 Mar 2026 22:21:53 -0700 SeongJae Park <[email protected]> wrote:
The
sysfs.pytest 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 <[email protected]>--- tools/testing/selftests/damon/sysfs.py | 31 ++++++++++++++++++++++++++ 1 file changed, 31 insertions(+)tools/testing/selftests/damon/sysfs.py +13
-0@@ -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:tools/testing/selftests/damon/sysfs.py def assert_ctx_committed(ctx, dump): · line 224
Quoted 10 lines
tools/testing/selftests/damon/sysfs.py +10
-0+ 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?
:
: Sincekd.commit()stages and commits the state of all contexts associated with : the kdamond, whenkd.commit()is called for the second context, the first : context's local pause attribute is already back to True.
:
: This would causekd.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.Quoted 5 lines
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 callkd.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:
'''
tools/testing/selftests/damon/sysfs.py +18
-15@@ -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']
Quoted 1 line
'''
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.
'''
tools/testing/selftests/damon/sysfs.py +12 -10
@@ -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