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 02/17] mm/damon/paddr: support PGIDLE_UNSET probe filter type
Date: Tue, 01 Sep 2026 04:41:10 +0000	[thread overview]
Message-ID: <20260901044110.B1F121F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901043417.2165-3-sj@kernel.org>

> Implement support of DAMON_FILTER_TYPE_PGIDLE_UNSET in the physical
> address space DAMON operations set.  It reuses damon_folio_young(),
> which was being used for access monitoring.
> 
> 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/20260901043417.2165-1-sj@kernel.org?part=2


  reply	other threads:[~2026-09-01  4:41 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01  4:33 [PATCH 00/17] mm/damon: introduce data access-as-a-data attribute SJ Park
2026-09-01  4:33 ` [PATCH 01/17] mm/damon/core: introduce DAMON_FILTER_TYPE_PGIDLE_UNSET SJ Park
2026-09-01  4:41   ` sashiko-bot
2026-09-01  4:33 ` [PATCH 02/17] mm/damon/paddr: support PGIDLE_UNSET probe filter type SJ Park
2026-09-01  4:41   ` sashiko-bot [this message]
2026-09-01  4:33 ` [PATCH 03/17] mm/damon/sysfs: support pgidle_unset " SJ Park
2026-09-01  4:42   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 04/17] Docs/mm/damon/design: document " SJ Park
2026-09-01  4:35   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 05/17] mm/damon/core: introduce damon_prep struct SJ Park
2026-09-01  4:46   ` sashiko-bot
2026-09-01  5:01     ` SJ Park
2026-09-01  4:34 ` [PATCH 06/17] mm/damon/core: commit preps SJ Park
2026-09-01  4:43   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 07/17] mm/damon/core: introduce damon_operations->prep_probes() SJ Park
2026-09-01  4:40   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 08/17] mm/damon/paddr: support damon_prep SJ Park
2026-09-01  4:47   ` sashiko-bot
2026-09-01  5:05     ` SJ Park
2026-09-01  4:34 ` [PATCH 09/17] mm/damon/sysfs: implement preps directory SJ Park
2026-09-01  4:40   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 10/17] mm/damon/sysfs: implement preps/nr_preps file SJ Park
2026-09-01  4:42   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 11/17] mm/damon/sysfs: create directories for nr_preps writes SJ Park
2026-09-01  4:40   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 12/17] mm/damon/sysfs: implement prep_action file SJ Park
2026-09-01  4:40   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 13/17] mm/damon/sysfs: pass preps to DAMON core SJ Park
2026-09-01  4:53   ` sashiko-bot
2026-09-01  5:24     ` SJ Park
2026-09-01  4:34 ` [PATCH 14/17] selftests/damon/sysfs.sh: test probe prep sysfs files SJ Park
2026-09-01  4:36   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 15/17] Docs/mm/damon/design: document probe preps SJ Park
2026-09-01  4:35   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 16/17] Docs/admin-guide/mm/damon/usage: document probe preps sysfs files SJ Park
2026-09-01  4:38   ` sashiko-bot
2026-09-01  4:34 ` [PATCH 17/17] Docs/ABI/damon: document probe prep " SJ Park
2026-09-01  4:36   ` sashiko-bot
2026-09-01  5:26 ` [PATCH 00/17] mm/damon: introduce data access-as-a-data attribute 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=20260901044110.B1F121F000E9@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