DAMON development mailing list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH v1.1 03/17] mm/damon/sysfs: support pgidle_unset probe filter type
Date: Tue, 01 Sep 2026 13:34:46 +0000	[thread overview]
Message-ID: <20260901133446.F2AC61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901132506.99243-4-sj@kernel.org>

> Extend DAMON sysfs interface to allow users to set
> DAMON_FILTER_TYPE_PGIDLE_UNSET by writing 'pgidle_unset' to the probe
> filter type file.
> 
> Signed-off-by: SJ Park <sj@kernel.org>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260901132506.99243-1-sj@kernel.org?part=3


  reply	other threads:[~2026-09-01 13:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 13:24 [PATCH v1.1 00/17] mm/damon: introduce data access-as-a-data attribute SJ Park
2026-09-01 13:24 ` [PATCH v1.1 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET SJ Park
2026-09-01 13:32   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 02/17] mm/damon/paddr: support PGIDLE_UNSET probe filter type SJ Park
2026-09-01 13:37   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 03/17] mm/damon/sysfs: support pgidle_unset " SJ Park
2026-09-01 13:34   ` sashiko-bot [this message]
2026-09-01 13:24 ` [PATCH v1.1 04/17] Docs/mm/damon/design: document " SJ Park
2026-09-01 13:27   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 05/17] mm/damon/core: introduce damon_prep struct SJ Park
2026-09-01 13:36   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 06/17] mm/damon/core: commit preps SJ Park
2026-09-01 13:36   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 07/17] mm/damon/core: introduce damon_operations->prep_probes() SJ Park
2026-09-01 13:30   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 08/17] mm/damon/paddr: support damon_prep SJ Park
2026-09-01 13:32   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 09/17] mm/damon/sysfs: implement preps directory SJ Park
2026-09-01 13:34   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 10/17] mm/damon/sysfs: implement preps/nr_preps file SJ Park
2026-09-01 13:40   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 11/17] mm/damon/sysfs: create directories for nr_preps writes SJ Park
2026-09-01 13:37   ` sashiko-bot
2026-09-01 13:24 ` [PATCH v1.1 12/17] mm/damon/sysfs: implement prep_action file SJ Park
2026-09-01 13:46   ` sashiko-bot
2026-09-01 13:25 ` [PATCH v1.1 13/17] mm/damon/sysfs: pass preps to DAMON core SJ Park
2026-09-01 13:41   ` sashiko-bot
2026-09-01 13:25 ` [PATCH v1.1 14/17] selftests/damon/sysfs.sh: test probe prep sysfs files SJ Park
2026-09-01 13:38   ` sashiko-bot
2026-09-01 13:25 ` [PATCH v1.1 15/17] Docs/mm/damon/design: document probe preps SJ Park
2026-09-01 13:37   ` sashiko-bot
2026-09-01 13:25 ` [PATCH v1.1 16/17] Docs/admin-guide/mm/damon/usage: document probe preps sysfs files SJ Park
2026-09-01 13:39   ` sashiko-bot
2026-09-01 13:25 ` [PATCH v1.1 17/17] Docs/ABI/damon: document probe prep " SJ Park
2026-09-01 13:38   ` sashiko-bot
2026-09-01 17:18 ` [PATCH v1.1 00/17] mm/damon: introduce data access-as-a-data attribute Andrew Morton
2026-09-01 23:52   ` 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=20260901133446.F2AC61F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sj@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