The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Zeng Heng <zengheng4@huawei.com>
Cc: SeongJae Park <sj@kernel.org>,
	Ravi Jonnalagadda <ravis.opensrc@gmail.com>,
	akinobu.mita@gmail.com, damon@lists.linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, akpm@linux-foundation.org,
	corbet@lwn.net, bijan311@gmail.com, ajayjoshi@micron.com,
	honggyu.kim@sk.com, yunjeong.mun@sk.com
Subject: Re: [RFC PATCH 0/6] mm/damon: hardware-sampled access reports
Date: Tue, 23 Jun 2026 17:14:24 -0700	[thread overview]
Message-ID: <20260624001425.77489-1-sj@kernel.org> (raw)
In-Reply-To: <7d46a48c-8805-09e1-4818-807953898fb4@huawei.com>

Hello Zeng,

On Tue, 23 Jun 2026 22:08:03 +0800 Zeng Heng <zengheng4@huawei.com> wrote:

> Hi Ravi,
> 
> On 2026/5/30 0:56, Ravi Jonnalagadda wrote:
> > This series introduces a vendor and PMU-agnostic substrate inside DAMON
> > that consumes hardware-sampled access reports through the standard
> > perf-event interface.  Userspace selects the PMU through sysfs (raw
> > type/config knobs), driving either Intel PEBS L3-miss sampling or AMD
> > IBS Op sampling.
> > 
> 
> [...]
> 
> > 
> > Ravi Jonnalagadda (6):
> >    mm/damon: add struct damon_perf_event{,_attr} and per-ctx perf_events
> >      list
> >    mm/damon/sysfs-sample: expose perf_events configuration via sysfs
> >    mm/damon/sysfs: install perf_events on apply
> >    mm/damon/core: per-CPU SPSC ring drain and damon_perf_event lifecycle
> >    mm/damon/vaddr: implement perf-event access check
> >    mm/damon: add damos_node_eligible_mem_bp tracepoint
> > 
> >   include/linux/damon.h        |  80 +++++
> >   include/trace/events/damon.h |  49 +++
> >   mm/damon/core.c              | 403 ++++++++++++++++++++----
> >   mm/damon/ops-common.h        |  39 +++
> >   mm/damon/sysfs-common.h      |   6 +
> >   mm/damon/sysfs-sample.c      | 579 +++++++++++++++++++++++++++++++++++
> >   mm/damon/sysfs.c             |   3 +
> >   mm/damon/vaddr.c             | 267 ++++++++++++++++
> >   8 files changed, 1370 insertions(+), 56 deletions(-)
> > 
> > 
> > base-commit: 4c8ad15abf15eb480d3ad85f902001e35465ef18
> 
> I wasn't able to apply this patch series to the linux (and linux-next)
> mainline branch, and also had trouble identifying the source of the base
> commit.
> 
> Would you mind sharing where this baseline is from?

TLDR: I pushed [1] a tree having this series applied on top of the baseline to
GitHub.  Please feel free to use it.

I think the baseline was a commit on damon/next tree [2].  Because damon/next
is continuously rebased, we cannot get the commit in a simple way.  Fortunately
the commit is still available on my local tree.  So I applied this patch series
on top of the commit and pushed [1] to a branch of DAMON kernel tree at GitHub.

Note that the branch is not guaranteed to exist there for long term.  But
hopefully this series will be merged into the mainline before that.

[1] https://github.com/damonitor/linux/tree/ravi_hw_sampled_access_reports_rfc_v1
[2] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees


Thanks,
SJ

[...]

  reply	other threads:[~2026-06-24  0:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 16:56 [RFC PATCH 0/6] mm/damon: hardware-sampled access reports Ravi Jonnalagadda
2026-05-29 16:56 ` [RFC PATCH 1/6] mm/damon: add struct damon_perf_event{,_attr} and per-ctx perf_events list Ravi Jonnalagadda
2026-05-29 16:56 ` [RFC PATCH 2/6] mm/damon/sysfs-sample: expose perf_events configuration via sysfs Ravi Jonnalagadda
2026-05-29 16:56 ` [RFC PATCH 3/6] mm/damon/sysfs: install perf_events on apply Ravi Jonnalagadda
2026-05-29 16:56 ` [RFC PATCH 4/6] mm/damon/core: per-CPU SPSC ring drain and damon_perf_event lifecycle Ravi Jonnalagadda
2026-05-29 16:56 ` [RFC PATCH 5/6] mm/damon/vaddr: implement perf-event access check Ravi Jonnalagadda
2026-05-29 16:56 ` [RFC PATCH 6/6] mm/damon: add damos_node_eligible_mem_bp tracepoint Ravi Jonnalagadda
2026-05-30  0:04 ` [RFC PATCH 0/6] mm/damon: hardware-sampled access reports SeongJae Park
2026-05-30  3:01   ` Akinobu Mita
2026-05-30  5:03     ` Ravi Jonnalagadda
2026-06-23 14:08 ` Zeng Heng
2026-06-24  0:14   ` SeongJae Park [this message]
2026-06-24 11:23     ` Zeng Heng

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=20260624001425.77489-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=ajayjoshi@micron.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bijan311@gmail.com \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=honggyu.kim@sk.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ravis.opensrc@gmail.com \
    --cc=yunjeong.mun@sk.com \
    --cc=zengheng4@huawei.com \
    /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