Linux Perf Users
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	damon@lists.linux.dev, linux-perf-users@vger.kernel.org,
	ravis.opensrc@gmail.com
Subject: Re: [RFC PATCH 0/2] damo: support perf event configuration
Date: Tue, 23 Jun 2026 06:49:49 -0700	[thread overview]
Message-ID: <20260623134951.67000-1-sj@kernel.org> (raw)
In-Reply-To: <CAC5umyi0v8Z3Frtr4yL_LRZu9O7wWF1HZfVbutagORde_i-7XQ@mail.gmail.com>

On Tue, 23 Jun 2026 22:29:42 +0900 Akinobu Mita <akinobu.mita@gmail.com> wrote:

> 2026年6月23日(火) 0:24 SeongJae Park <sj@kernel.org>:
> >
> > Hello Akinobu,
> >
> > On Mon, 22 Jun 2026 22:49:31 +0900 Akinobu Mita <akinobu.mita@gmail.com> wrote:
> >
> > > This patch set aims to make it easier to specify the perf event settings
> > > proposed for DAMON by Ravi's hardware-sampled access reports patch set [1]
> > > from the damo tool.
> >
> > Seems this patch is built on top of the per-CPU/thread/read/write monitoring
> > patch series [1].  We made a plan [2] to use another user interface, though.
> > The plan is, making the interface ready for page table accessed bits based
> > monitoring by LPC'26 (milestone 1), and implementing the perf event based
> > monitoring on top of it, by LSFMMBPF'27 (milestone 2).
> >
> > So the eventual damo part change for supporting perf event based monitoring
> > will be quite different from this series.  I guess you are sharing this series
> > not because you aiming to merge it as is right now, but just for sharing the
> > code with other stakeholders like Ravis, not me?  If I'm not wrong, I will skip
> > this series for now, to focus on the milestone 1.
> 
> Since I will align with the final user interface later, please focus on
> the optimal interface for Milestone 1 without worrying about that.

Thank you, Akinobu.

> 
> > Please let me know if you want more of my feedback.
> 
> However, even if the interface ends up being completely different from the
> current one, I believe that enabling configuration via `damo` using
> symbolic event names like this would still require calling the perf
> python interface (`import perf`) from damo and modifying the `perf` tool
> itself; could you please check if that approach is acceptable?

I'm bit concerned at having such dependencies.  I'd prefer making DAMON sysfs
interface uses a symbolic names and just use it from damo if possible.  If that
is not possible, could you share more details about why such changes are
required?  I'm still lazily delaying studying about perf events, so please bear
in mind with me.

> 
> Thank you for your continued excellent work on improving DAMON.

Thank you for your grateful contributions, too!


Thanks,
SJ

[...]

      reply	other threads:[~2026-06-23 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 13:49 [RFC PATCH 0/2] damo: support perf event configuration Akinobu Mita
2026-06-22 13:49 ` [RFC PATCH 1/2] perf python: Add access to various members of evsel Akinobu Mita
2026-06-23 18:10   ` Ian Rogers
2026-06-22 13:49 ` [RFC PATCH 2/2] damo: add --perf_event option Akinobu Mita
2026-06-22 15:24 ` [RFC PATCH 0/2] damo: support perf event configuration SeongJae Park
2026-06-23 13:29   ` Akinobu Mita
2026-06-23 13:49     ` SeongJae 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=20260623134951.67000-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akinobu.mita@gmail.com \
    --cc=damon@lists.linux.dev \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=ravis.opensrc@gmail.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