public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Gutierrez Asier <gutierrez.asier@huawei-partners.com>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	<damon@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>
Subject: Re: [RFC PATCH 02/19] mm/damon/core: embed damon_probe objects in damon_ctx
Date: Mon, 27 Apr 2026 16:18:14 +0300	[thread overview]
Message-ID: <2e2bee93-d68c-4b29-9ad1-1ef975fccec4@huawei-partners.com> (raw)
In-Reply-To: <20260426205222.93895-3-sj@kernel.org>



On 4/26/2026 11:52 PM, SeongJae Park wrote:
> Let damon_probe objects be able to be installed on a given damon_ctx, by
> adding a linked list header for storing the objects.  Add initialization
> and cleanup of the new field with helper functions, too.
> 
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
>  include/linux/damon.h |  9 +++++++++
>  mm/damon/core.c       | 38 ++++++++++++++++++++++++++++++++++++++
>  2 files changed, 47 insertions(+)
> 
> diff --git a/include/linux/damon.h b/include/linux/damon.h
> index da2f026eac725..65d7ee0a70ac0 100644
> --- a/include/linux/damon.h
> +++ b/include/linux/damon.h
> @@ -859,6 +859,7 @@ struct damon_ctx {
>  
>  /* public: */
>  	struct damon_operations ops;
> +	struct list_head probes;
>  	unsigned long addr_unit;
>  	unsigned long min_region_sz;
>  	bool pause;
> @@ -892,6 +893,11 @@ static inline unsigned long damon_sz_region(struct damon_region *r)
>  	return r->ar.end - r->ar.start;
>  }
>  
> +#define damon_for_each_probe(p, ctx) \
> +	list_for_each_entry(p, &ctx->probes, list)
> +
> +#define damon_for_each_probe_safe(p, next, ctx) \
> +	list_for_each_entry_safe(p, next, &ctx->probes, list)
>  
>  #define damon_for_each_region(r, t) \
>  	list_for_each_entry(r, &t->regions_list, list)
> @@ -934,6 +940,9 @@ static inline unsigned long damon_sz_region(struct damon_region *r)
>  
>  #ifdef CONFIG_DAMON
>  
> +struct damon_probe *damon_new_probe(void);
> +void damon_add_probe(struct damon_ctx *ctx, struct damon_probe *probe);
> +
>  struct damon_region *damon_new_region(unsigned long start, unsigned long end);
>  
>  int damon_set_regions(struct damon_target *t, struct damon_addr_range *ranges,
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index f556786597c83..861ab977d1edf 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
> @@ -109,6 +109,38 @@ int damon_select_ops(struct damon_ctx *ctx, enum damon_ops_id id)
>  	return err;
>  }
>  
> +struct damon_probe *damon_new_probe(void)
> +{
> +	struct damon_probe *p;
> +
> +	p = kmalloc_obj(*p);
> +	if (!p)
> +		return NULL;
> +	INIT_LIST_HEAD(&p->list);
> +	return p;
> +}
> +
> +void damon_add_probe(struct damon_ctx *ctx, struct damon_probe *probe)
> +{
> +	list_add_tail(&probe->list, &ctx->probes);
> +}
> +
> +static void damon_del_probe(struct damon_probe *p)
> +{
> +	list_del(&p->list);
> +}
> +
> +static void damon_free_probe(struct damon_probe *p)
> +{
> +	kfree(p);
> +}
> +
> +static void damon_destroy_probe(struct damon_probe *p)
> +{
> +	damon_del_probe(p);
> +	damon_free_probe(p);

Why don't we inline list_del and kfree here instead of calling
damon_del/free_probe?

> +}
> +
>  #ifdef CONFIG_DAMON_DEBUG_SANITY
>  static void damon_verify_new_region(unsigned long start, unsigned long end)
>  {
> @@ -633,6 +665,8 @@ struct damon_ctx *damon_new_ctx(void)
>  	ctx->attrs.min_nr_regions = 10;
>  	ctx->attrs.max_nr_regions = 1000;
>  
> +	INIT_LIST_HEAD(&ctx->probes);
> +
>  	ctx->addr_unit = 1;
>  	ctx->min_region_sz = DAMON_MIN_REGION_SZ;
>  
> @@ -653,12 +687,16 @@ static void damon_destroy_targets(struct damon_ctx *ctx)
>  void damon_destroy_ctx(struct damon_ctx *ctx)
>  {
>  	struct damos *s, *next_s;
> +	struct damon_probe *p, *next_p;
>  
>  	damon_destroy_targets(ctx);
>  
>  	damon_for_each_scheme_safe(s, next_s, ctx)
>  		damon_destroy_scheme(s);
>  
> +	damon_for_each_probe_safe(p, next_p, ctx)
> +		damon_destroy_probe(p);
> +
>  	kfree(ctx);
>  }
>  

-- 
Asier Gutierrez
Huawei



  reply	other threads:[~2026-04-27 13:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26 20:52 [RFC PATCH 00/19] mm/damon: introduce data attributes monitoring SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 01/19] mm/damon/core: introduce struct damon_probe SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 02/19] mm/damon/core: embed damon_probe objects in damon_ctx SeongJae Park
2026-04-27 13:18   ` Gutierrez Asier [this message]
2026-04-28  0:35     ` SeongJae Park
2026-04-28 13:09       ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 03/19] mm/damon/core: introduce damon_filter SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 04/19] mm/damon/core: commit probes SeongJae Park
2026-04-27 13:21   ` Gutierrez Asier
2026-04-28  0:39     ` SeongJae Park
2026-04-28 13:13       ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 05/19] mm/damon/core: introduce damon_region->probe_hits SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 06/19] mm/damon/core: introduce damon_ops->apply_probes SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 07/19] mm/damon/core: do data attributes monitoring SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 08/19] mm/damon/paddr: support " SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 09/19] mm/damon/sysfs: implement probes dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 10/19] mm/damon/sysfs: implement probe dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 11/19] mm/damon/sysfs: implement filters directory SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 12/19] mm/damon/sysfs: implement filter dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 13/19] mm/damon/sysfs: implement filter dir files SeongJae Park
2026-04-27 13:24   ` Gutierrez Asier
2026-04-28  0:44     ` SeongJae Park
2026-04-28 13:10       ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 14/19] mm/damon/sysfs: setup probes on DAMON core API parameters SeongJae Park
2026-04-27 13:25   ` Gutierrez Asier
2026-04-28  0:48     ` SeongJae Park
2026-04-28 13:08       ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 15/19] mm/damon/sysfs-schemes: implement tried_region/probe_hits file SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 16/19] mm/damon: trace probe_hits SeongJae Park
2026-04-28 18:17   ` Steven Rostedt
2026-04-29  0:13     ` SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 17/19] selftests/damon/sysfs.sh: test probes dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 18/19] Docs/mm/damon/design: document data attributes monitoring SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 19/19] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2026-04-27 13:16 ` [RFC PATCH 00/19] mm/damon: introduce " Gutierrez Asier
2026-04-28  0:33   ` SeongJae 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=2e2bee93-d68c-4b29-9ad1-1ef975fccec4@huawei-partners.com \
    --to=gutierrez.asier@huawei-partners.com \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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