2021-09-07 19:56:48 -07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
|
|
|
|
#undef TRACE_SYSTEM
|
|
|
|
|
#define TRACE_SYSTEM damon
|
|
|
|
|
|
|
|
|
|
#if !defined(_TRACE_DAMON_H) || defined(TRACE_HEADER_MULTI_READ)
|
|
|
|
|
#define _TRACE_DAMON_H
|
|
|
|
|
|
|
|
|
|
#include <linux/damon.h>
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
|
#include <linux/tracepoint.h>
|
|
|
|
|
|
2025-07-04 15:14:08 -07:00
|
|
|
TRACE_EVENT(damos_esz,
|
|
|
|
|
|
|
|
|
|
TP_PROTO(unsigned int context_idx, unsigned int scheme_idx,
|
|
|
|
|
unsigned long esz),
|
|
|
|
|
|
|
|
|
|
TP_ARGS(context_idx, scheme_idx, esz),
|
|
|
|
|
|
|
|
|
|
TP_STRUCT__entry(
|
|
|
|
|
__field(unsigned int, context_idx)
|
|
|
|
|
__field(unsigned int, scheme_idx)
|
|
|
|
|
__field(unsigned long, esz)
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_fast_assign(
|
|
|
|
|
__entry->context_idx = context_idx;
|
|
|
|
|
__entry->scheme_idx = scheme_idx;
|
|
|
|
|
__entry->esz = esz;
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_printk("ctx_idx=%u scheme_idx=%u esz=%lu",
|
|
|
|
|
__entry->context_idx, __entry->scheme_idx,
|
|
|
|
|
__entry->esz)
|
|
|
|
|
);
|
|
|
|
|
|
mm/damon/core: add a tracepoint for damos apply target regions
Patch series "mm/damon: add a tracepoint for damos apply target regions",
v2.
DAMON provides damon_aggregated tracepoint to let users record full
monitoring results. Sometimes, users need to record monitoring results of
specific pattern. DAMOS tried regions directory of DAMON sysfs interface
allows it, but the interface is mainly designed for snapshots and
therefore would be inefficient for such recording. Implement yet another
tracepoint for efficient support of the usecase.
This patch (of 2):
DAMON provides damon_aggregated tracepoint, which exposes details of each
region and its access monitoring results. It is useful for getting whole
monitoring results, e.g., for recording purposes.
For investigations of DAMOS, DAMON Sysfs interface provides DAMOS
statistics and tried_regions directory. But, those provides only
statistics and snapshots. If the scheme is frequently applied and if the
user needs to know every detail of DAMOS behavior, the snapshot-based
interface could be insufficient and expensive.
As a last resort, userspace users need to record the all monitoring
results via damon_aggregated tracepoint and simulate how DAMOS would
worked. It is unnecessarily complicated. DAMON kernel API users,
meanwhile, can do that easily via before_damos_apply() callback field of
'struct damon_callback', though.
Add a tracepoint that will be called just after before_damos_apply()
callback for more convenient investigations of DAMOS. The tracepoint
exposes all details about each regions, similar to damon_aggregated
tracepoint.
Please note that DAMOS is currently not only for memory management but
also for query-like efficient monitoring results retrievals (when 'stat'
action is used). Until now, only statistics or snapshots were supported.
Addition of this tracepoint allows efficient full recording of DAMOS-based
filtered monitoring results.
Link: https://lkml.kernel.org/r/20230913022050.2109-1-sj@kernel.org
Link: https://lkml.kernel.org/r/20230913022050.2109-2-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org> [tracing]
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2023-09-13 02:20:49 +00:00
|
|
|
TRACE_EVENT_CONDITION(damos_before_apply,
|
|
|
|
|
|
|
|
|
|
TP_PROTO(unsigned int context_idx, unsigned int scheme_idx,
|
|
|
|
|
unsigned int target_idx, struct damon_region *r,
|
|
|
|
|
unsigned int nr_regions, bool do_trace),
|
|
|
|
|
|
2024-11-15 10:20:23 -08:00
|
|
|
TP_ARGS(context_idx, scheme_idx, target_idx, r, nr_regions, do_trace),
|
mm/damon/core: add a tracepoint for damos apply target regions
Patch series "mm/damon: add a tracepoint for damos apply target regions",
v2.
DAMON provides damon_aggregated tracepoint to let users record full
monitoring results. Sometimes, users need to record monitoring results of
specific pattern. DAMOS tried regions directory of DAMON sysfs interface
allows it, but the interface is mainly designed for snapshots and
therefore would be inefficient for such recording. Implement yet another
tracepoint for efficient support of the usecase.
This patch (of 2):
DAMON provides damon_aggregated tracepoint, which exposes details of each
region and its access monitoring results. It is useful for getting whole
monitoring results, e.g., for recording purposes.
For investigations of DAMOS, DAMON Sysfs interface provides DAMOS
statistics and tried_regions directory. But, those provides only
statistics and snapshots. If the scheme is frequently applied and if the
user needs to know every detail of DAMOS behavior, the snapshot-based
interface could be insufficient and expensive.
As a last resort, userspace users need to record the all monitoring
results via damon_aggregated tracepoint and simulate how DAMOS would
worked. It is unnecessarily complicated. DAMON kernel API users,
meanwhile, can do that easily via before_damos_apply() callback field of
'struct damon_callback', though.
Add a tracepoint that will be called just after before_damos_apply()
callback for more convenient investigations of DAMOS. The tracepoint
exposes all details about each regions, similar to damon_aggregated
tracepoint.
Please note that DAMOS is currently not only for memory management but
also for query-like efficient monitoring results retrievals (when 'stat'
action is used). Until now, only statistics or snapshots were supported.
Addition of this tracepoint allows efficient full recording of DAMOS-based
filtered monitoring results.
Link: https://lkml.kernel.org/r/20230913022050.2109-1-sj@kernel.org
Link: https://lkml.kernel.org/r/20230913022050.2109-2-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org> [tracing]
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2023-09-13 02:20:49 +00:00
|
|
|
|
|
|
|
|
TP_CONDITION(do_trace),
|
|
|
|
|
|
|
|
|
|
TP_STRUCT__entry(
|
|
|
|
|
__field(unsigned int, context_idx)
|
|
|
|
|
__field(unsigned int, scheme_idx)
|
|
|
|
|
__field(unsigned long, target_idx)
|
|
|
|
|
__field(unsigned long, start)
|
|
|
|
|
__field(unsigned long, end)
|
|
|
|
|
__field(unsigned int, nr_accesses)
|
|
|
|
|
__field(unsigned int, age)
|
|
|
|
|
__field(unsigned int, nr_regions)
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_fast_assign(
|
|
|
|
|
__entry->context_idx = context_idx;
|
|
|
|
|
__entry->scheme_idx = scheme_idx;
|
|
|
|
|
__entry->target_idx = target_idx;
|
|
|
|
|
__entry->start = r->ar.start;
|
|
|
|
|
__entry->end = r->ar.end;
|
2023-09-16 02:09:39 +00:00
|
|
|
__entry->nr_accesses = r->nr_accesses_bp / 10000;
|
mm/damon/core: add a tracepoint for damos apply target regions
Patch series "mm/damon: add a tracepoint for damos apply target regions",
v2.
DAMON provides damon_aggregated tracepoint to let users record full
monitoring results. Sometimes, users need to record monitoring results of
specific pattern. DAMOS tried regions directory of DAMON sysfs interface
allows it, but the interface is mainly designed for snapshots and
therefore would be inefficient for such recording. Implement yet another
tracepoint for efficient support of the usecase.
This patch (of 2):
DAMON provides damon_aggregated tracepoint, which exposes details of each
region and its access monitoring results. It is useful for getting whole
monitoring results, e.g., for recording purposes.
For investigations of DAMOS, DAMON Sysfs interface provides DAMOS
statistics and tried_regions directory. But, those provides only
statistics and snapshots. If the scheme is frequently applied and if the
user needs to know every detail of DAMOS behavior, the snapshot-based
interface could be insufficient and expensive.
As a last resort, userspace users need to record the all monitoring
results via damon_aggregated tracepoint and simulate how DAMOS would
worked. It is unnecessarily complicated. DAMON kernel API users,
meanwhile, can do that easily via before_damos_apply() callback field of
'struct damon_callback', though.
Add a tracepoint that will be called just after before_damos_apply()
callback for more convenient investigations of DAMOS. The tracepoint
exposes all details about each regions, similar to damon_aggregated
tracepoint.
Please note that DAMOS is currently not only for memory management but
also for query-like efficient monitoring results retrievals (when 'stat'
action is used). Until now, only statistics or snapshots were supported.
Addition of this tracepoint allows efficient full recording of DAMOS-based
filtered monitoring results.
Link: https://lkml.kernel.org/r/20230913022050.2109-1-sj@kernel.org
Link: https://lkml.kernel.org/r/20230913022050.2109-2-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org> [tracing]
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2023-09-13 02:20:49 +00:00
|
|
|
__entry->age = r->age;
|
|
|
|
|
__entry->nr_regions = nr_regions;
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_printk("ctx_idx=%u scheme_idx=%u target_idx=%lu nr_regions=%u %lu-%lu: %u %u",
|
|
|
|
|
__entry->context_idx, __entry->scheme_idx,
|
|
|
|
|
__entry->target_idx, __entry->nr_regions,
|
|
|
|
|
__entry->start, __entry->end,
|
|
|
|
|
__entry->nr_accesses, __entry->age)
|
|
|
|
|
);
|
|
|
|
|
|
2025-07-04 15:14:07 -07:00
|
|
|
TRACE_EVENT(damon_monitor_intervals_tune,
|
|
|
|
|
|
|
|
|
|
TP_PROTO(unsigned long sample_us),
|
|
|
|
|
|
|
|
|
|
TP_ARGS(sample_us),
|
|
|
|
|
|
|
|
|
|
TP_STRUCT__entry(
|
|
|
|
|
__field(unsigned long, sample_us)
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_fast_assign(
|
|
|
|
|
__entry->sample_us = sample_us;
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_printk("sample_us=%lu", __entry->sample_us)
|
|
|
|
|
);
|
|
|
|
|
|
2021-09-07 19:56:48 -07:00
|
|
|
TRACE_EVENT(damon_aggregated,
|
|
|
|
|
|
2023-09-07 02:29:29 +00:00
|
|
|
TP_PROTO(unsigned int target_id, struct damon_region *r,
|
|
|
|
|
unsigned int nr_regions),
|
2021-09-07 19:56:48 -07:00
|
|
|
|
2023-09-07 02:29:29 +00:00
|
|
|
TP_ARGS(target_id, r, nr_regions),
|
2021-09-07 19:56:48 -07:00
|
|
|
|
|
|
|
|
TP_STRUCT__entry(
|
|
|
|
|
__field(unsigned long, target_id)
|
|
|
|
|
__field(unsigned int, nr_regions)
|
|
|
|
|
__field(unsigned long, start)
|
|
|
|
|
__field(unsigned long, end)
|
|
|
|
|
__field(unsigned int, nr_accesses)
|
2022-01-14 14:09:37 -08:00
|
|
|
__field(unsigned int, age)
|
2021-09-07 19:56:48 -07:00
|
|
|
),
|
|
|
|
|
|
|
|
|
|
TP_fast_assign(
|
2022-01-14 14:10:50 -08:00
|
|
|
__entry->target_id = target_id;
|
2021-09-07 19:56:48 -07:00
|
|
|
__entry->nr_regions = nr_regions;
|
|
|
|
|
__entry->start = r->ar.start;
|
|
|
|
|
__entry->end = r->ar.end;
|
|
|
|
|
__entry->nr_accesses = r->nr_accesses;
|
2022-01-14 14:09:37 -08:00
|
|
|
__entry->age = r->age;
|
2021-09-07 19:56:48 -07:00
|
|
|
),
|
|
|
|
|
|
2022-01-14 14:09:37 -08:00
|
|
|
TP_printk("target_id=%lu nr_regions=%u %lu-%lu: %u %u",
|
2021-09-07 19:56:48 -07:00
|
|
|
__entry->target_id, __entry->nr_regions,
|
2022-01-14 14:09:37 -08:00
|
|
|
__entry->start, __entry->end,
|
|
|
|
|
__entry->nr_accesses, __entry->age)
|
2021-09-07 19:56:48 -07:00
|
|
|
);
|
|
|
|
|
|
|
|
|
|
#endif /* _TRACE_DAMON_H */
|
|
|
|
|
|
|
|
|
|
/* This part must be outside protection */
|
|
|
|
|
#include <trace/define_trace.h>
|