From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET
Date: Sat, 25 Jul 2026 14:28:58 -0700 [thread overview]
Message-ID: <20260725212900.130853-1-sj@kernel.org> (raw)
In-Reply-To: <20260725211157.0B22D1F000E9@smtp.kernel.org>
On Sat, 25 Jul 2026 21:11:56 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The commit introduces `DAMON_FILTER_TYPE_PGIDLE_UNSET` but entirely omits its implementation in both the filter evaluation logic and the sysfs interface.
> --
>
> --- Patch [1]: [RFC PATCH 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET ---
> commit 227024f25ad71dec25a7b05a4270affaab5be023
> Author: SJ Park <sj@kernel.org>
>
> mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET
>
> Introduce a new DAMON filter type, pgidle_unset. It will match pages
> that have their PG_Idle flag unset, or the page table accessed bit set.
>
> > diff --git a/include/linux/damon.h b/include/linux/damon.h
> > index 0c8b7ddef9abb..a8bb9ee6979e3 100644
> > --- a/include/linux/damon.h
> > +++ b/include/linux/damon.h
> [ ... ]
> > @@ -742,12 +742,14 @@ struct damon_intervals_goal {
> > /**
> > * enum damon_filter_type - Type of &struct damon_filter
> > *
> > - * @DAMON_FILTER_TYPE_ANON: Anonymous pages.
> > - * @DAMON_FILTER_TYPE_MEMCG: Specific memcg's pages.
> > + * @DAMON_FILTER_TYPE_ANON: Anonymous pages.
> > + * @DAMON_FILTER_TYPE_MEMCG: Specific memcg's pages.
> > + * @DAMON_FILTER_TYPE_PGIDLE_UNSET: Pgidle is unset.
> > */
> > enum damon_filter_type {
> > DAMON_FILTER_TYPE_ANON,
> > DAMON_FILTER_TYPE_MEMCG,
> > + DAMON_FILTER_TYPE_PGIDLE_UNSET,
>
> [Severity: Medium]
> Is the implementation for this new filter type missing from the filter
> evaluation logic?
>
> Looking at damon_pa_filter_match() in mm/damon/paddr.c, the switch
> statement evaluates filters but lacks a case to process the newly
> introduced type:
>
> mm/damon/paddr.c:damon_pa_filter_match() {
> ...
> switch (filter->type) {
> case DAMON_FILTER_TYPE_ANON:
> ...
> }
>
> Will this cause the evaluation to fall through to a default case and behave
> incorrectly rather than matching the PG_Idle or accessed bit as intended?
>
> Also, does this new type need to be mapped in the sysfs interface so userspace
> can configure it? The damon_sysfs_filter_type_names array in mm/damon/sysfs.c
> doesn't seem to include the new mapping:
>
> mm/damon/sysfs.c: {
> ...
> static const struct damon_sysfs_filter_type_name
> damon_sysfs_filter_type_names[] = {
> ...
> }
That will be introduced in a later patch of this series.
>
> > };
> >
> > /**
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260725210225.129944-1-sj@kernel.org?part=1
Thanks,
SJ
next prev parent reply other threads:[~2026-07-25 21:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 21:02 [RFC PATCH 00/17] mm/damon: introduce data access-as-a-data attribute SJ Park
2026-07-25 21:02 ` [RFC PATCH 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET SJ Park
2026-07-25 21:11 ` sashiko-bot
2026-07-25 21:28 ` SJ Park [this message]
2026-07-25 21:02 ` [RFC PATCH 02/17] mm/damon/paddr: support PGIDLE_UNSET probe filter type SJ Park
2026-07-25 21:17 ` sashiko-bot
2026-07-25 21:30 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 03/17] mm/damon/sysfs: support pgidle_unset " SJ Park
2026-07-25 21:02 ` [RFC PATCH 04/17] Docs/mm/damon/design: document " SJ Park
2026-07-25 21:05 ` sashiko-bot
2026-07-25 21:39 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 05/17] mm/damon/core: introduce damon_prep struct SJ Park
2026-07-25 21:02 ` [RFC PATCH 06/17] mm/damon/core: commit preps SJ Park
2026-07-25 21:02 ` [RFC PATCH 07/17] mm/damon/core: introduce damon_operations->prep_probes() SJ Park
2026-07-25 21:14 ` sashiko-bot
2026-07-25 21:52 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 08/17] mm/damon/paddr: support damon_prep SJ Park
2026-07-25 21:15 ` sashiko-bot
2026-07-25 21:54 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 09/17] mm/damon/sysfs: implement preps directory SJ Park
2026-07-25 21:13 ` sashiko-bot
2026-07-25 21:57 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 10/17] mm/damon/sysfs: create probe " SJ Park
2026-07-25 21:02 ` [RFC PATCH 11/17] mm/damon/sysfs: implement probe prep directory SJ Park
2026-07-25 21:10 ` sashiko-bot
2026-07-25 21:59 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 12/17] mm/damon/sysfs: create probe prep files for preps/nr file write SJ Park
2026-07-25 21:02 ` [RFC PATCH 13/17] mm/damon/sysfs: pass preps to DAMON core SJ Park
2026-07-25 21:02 ` [RFC PATCH 14/17] selftests/damon/sysfs.sh: test probe prep sysfs files SJ Park
2026-07-25 21:02 ` [RFC PATCH 15/17] Docs/mm/damon/design: document probe preps SJ Park
2026-07-25 21:06 ` sashiko-bot
2026-07-25 22:00 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 16/17] Docs/admin-guide/mm/damon/usage: document probe preps sysfs files SJ Park
2026-07-25 21:08 ` sashiko-bot
2026-07-25 22:06 ` SJ Park
2026-07-25 21:02 ` [RFC PATCH 17/17] Docs/ABI/damon: document probe prep " SJ Park
2026-07-25 21:12 ` sashiko-bot
2026-07-25 22:09 ` SJ 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=20260725212900.130853-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox