From: SeongJae Park <sj@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 12/12] mm/damon/core: add trace point for damos stat per apply interval
Date: Wed, 17 Dec 2025 15:52:18 -0800 [thread overview]
Message-ID: <20251217235219.2750-1-sj@kernel.org> (raw)
In-Reply-To: <20251217174851.28e7c4e5@gandalf.local.home>
On Wed, 17 Dec 2025 17:48:51 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 16 Dec 2025 00:01:25 -0800
> SeongJae Park <sj@kernel.org> wrote:
>
> > + TP_printk("ctx_idx=%u scheme_idx=%u nr_tried=%lu sz_tried=%lu "
> > + "nr_applied=%lu sz_tried=%lu sz_ops_filter_passed=%lu "
> > + "qt_exceeds=%lu nr_snapshots=%lu",
>
> Nit, but it's been stated that strings should not be broken up because of
> the column limit.
I also found checkpatch.pl shows warning for that. I was ignoring that since I
was thinking that's just a recommendation. But as I got more than one warning,
now I'd like to fix this.
Andrew, could you please add below attaching fixup patch?
>
> > + __entry->context_idx, __entry->scheme_idx,
> > + __entry->nr_tried, __entry->sz_tried,
> > + __entry->nr_applied, __entry->sz_applied,
> > + __entry->sz_ops_filter_passed, __entry->qt_exceeds,
> > + __entry->nr_snapshots)
> > +);
> > +
> > TRACE_EVENT(damos_esz,
> >
> > TP_PROTO(unsigned int context_idx, unsigned int scheme_idx,
> > diff --git a/mm/damon/core.c b/mm/damon/core.c
> > index 8908aec6670f..68dd2f7acba2 100644
> > --- a/mm/damon/core.c
> > +++ b/mm/damon/core.c
> > @@ -2256,6 +2256,22 @@ static void damos_adjust_quota(struct damon_ctx *c, struct damos *s)
> > quota->min_score = score;
> > }
> >
> > +static void damos_trace_stat(struct damon_ctx *c, struct damos *s)
> > +{
> > + unsigned int cidx = 0, sidx = 0;
> > + struct damos *siter;
> > +
> > + if (!trace_damos_stat_after_apply_interval_enabled())
> > + return;
>
> Other than that, from a tracing POV:
>
> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Thank you! :)
Thanks,
SJ
[...]
=== >8 ===
From 67a7762ee1ade258c53913ea4ecf9bafd4746ea9 Mon Sep 17 00:00:00 2001
From: SeongJae Park <sj@kernel.org>
Date: Wed, 17 Dec 2025 15:42:06 -0800
Subject: [PATCH] mm/damon: do not break the string for damos_stat tracepoint
The format string for damos_stat tracepoint is broken up to multiple
lines. Strings shouldn't be broken up due to the column limit, though.
Update the string to be put on a single line.
Suggested-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: SeongJae Park <sj@kernel.org>
---
include/trace/events/damon.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/trace/events/damon.h b/include/trace/events/damon.h
index 24fc402ab3c8..bf25ee07cb48 100644
--- a/include/trace/events/damon.h
+++ b/include/trace/events/damon.h
@@ -40,9 +40,7 @@ TRACE_EVENT(damos_stat_after_apply_interval,
__entry->nr_snapshots = stat->nr_snapshots;
),
- TP_printk("ctx_idx=%u scheme_idx=%u nr_tried=%lu sz_tried=%lu "
- "nr_applied=%lu sz_tried=%lu sz_ops_filter_passed=%lu "
- "qt_exceeds=%lu nr_snapshots=%lu",
+ TP_printk("ctx_idx=%u scheme_idx=%u nr_tried=%lu sz_tried=%lu nr_applied=%lu sz_tried=%lu sz_ops_filter_passed=%lu qt_exceeds=%lu nr_snapshots=%lu",
__entry->context_idx, __entry->scheme_idx,
__entry->nr_tried, __entry->sz_tried,
__entry->nr_applied, __entry->sz_applied,
--
2.47.3
next prev parent reply other threads:[~2025-12-17 23:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 8:01 [PATCH 00/12] mm/damon: introduce {,max_}nr_snapshots and tracepoint for damos stats SeongJae Park
2025-12-16 8:01 ` [PATCH 01/12] mm/damon/core: introduce nr_snapshots damos stat SeongJae Park
2026-01-14 12:29 ` Chris Mason
2026-01-14 15:20 ` SeongJae Park
2025-12-16 8:01 ` [PATCH 02/12] mm/damon/sysfs-schemes: introduce nr_snapshots damos stat file SeongJae Park
2025-12-16 8:01 ` [PATCH 03/12] Docs/mm/damon/design: update for nr_snapshots damos stat SeongJae Park
2025-12-16 8:01 ` [PATCH 04/12] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2025-12-16 8:01 ` [PATCH 05/12] Docs/ABI/damon: " SeongJae Park
2025-12-16 8:01 ` [PATCH 06/12] mm/damon: update damos kerneldoc for stat field SeongJae Park
2025-12-16 8:01 ` [PATCH 07/12] mm/damon/core: implement max_nr_snapshots SeongJae Park
2025-12-16 8:01 ` [PATCH 08/12] mm/damon/sysfs-schemes: implement max_nr_snapshots file SeongJae Park
2025-12-16 8:01 ` [PATCH 09/12] Docs/mm/damon/design: update for max_nr_snapshots SeongJae Park
2025-12-16 8:01 ` [PATCH 10/12] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2025-12-16 8:01 ` [PATCH 11/12] Docs/ABI/damon: " SeongJae Park
2025-12-16 8:01 ` [PATCH 12/12] mm/damon/core: add trace point for damos stat per apply interval SeongJae Park
2025-12-17 22:48 ` Steven Rostedt
2025-12-17 23:52 ` SeongJae Park [this message]
2025-12-18 2:29 ` Andrew Morton
2025-12-18 3:04 ` SeongJae Park
2025-12-18 17:29 ` Steven Rostedt
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=20251217235219.2750-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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.