DAMON development mailing list
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	David Hildenbrand <david@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
	Mike Rapoport <rppt@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Shuah Khan <shuah@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Vlastimil Babka <vbabka@kernel.org>,
	damon@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 00/17] mm/damon: introduce data access-as-a-data attribute
Date: Mon, 31 Aug 2026 22:26:26 -0700	[thread overview]
Message-ID: <20260901052627.6526-1-sj@kernel.org> (raw)
In-Reply-To: <20260901043417.2165-1-sj@kernel.org>

On Mon, 31 Aug 2026 21:33:56 -0700 SJ Park <sj@kernel.org> wrote:

> TL;DR: extend DAMON's data attributes monitoring system to support page
> table accessed bit and PG_idle based access monitoring.

Sashiko found [1] a possible race that is introduced by this series.  I will
fix it in the next revision.

[1] https://lore.kernel.org/20260901052446.4122-1-sj@kernel.org


Thanks,
SJ

[...]

      parent reply	other threads:[~2026-09-01  5:26 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
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 ` SJ Park [this message]

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=20260901052627.6526-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@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