From: SeongJae Park <sj@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: SeongJae Park <sj@kernel.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
damon@lists.linux.dev, linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/6] mm/damon/core: introduce struct damon_access_report
Date: Mon, 9 Mar 2026 18:23:27 -0700 [thread overview]
Message-ID: <20260310012329.93272-1-sj@kernel.org> (raw)
In-Reply-To: <CAP-5=fUPWNzFvsA0T3xJdGa1uQ2QgnZyphWys6AeFZNE54WXLQ@mail.gmail.com>
On Mon, 9 Mar 2026 08:19:53 -0700 Ian Rogers <irogers@google.com> wrote:
> On Sun, Mar 8, 2026 at 6:00 PM Akinobu Mita <akinobu.mita@gmail.com> wrote:
> >
> > The struct damon_access_report is borrowed from SeongJae Park's
> > DAMON extension project [1].
> >
> > [1] https://lore.kernel.org/linux-mm/20251208062943.68824-6-sj@kernel.org/T/
> > ---
> > include/linux/damon.h | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
> >
> > diff --git a/include/linux/damon.h b/include/linux/damon.h
> > index 49d2983af4a8..5f2870ae02ba 100644
> > --- a/include/linux/damon.h
> > +++ b/include/linux/damon.h
> > @@ -110,6 +110,30 @@ struct damon_target {
> > bool obsolete;
> > };
> >
> > +/**
> > + * struct damon_access_report - Represent single acces report information.
>
> nit: typo s/acces/access/
>
> > + * @paddr: Start physical address of the accessed address range.
> > + * @vaddr: Start virtual address of the accessed address range.
> > + * @size: The size of the accessed address range.
> > + * @cpu: The id of the CPU that made the access.
> > + * @tid: The task id of the task that made the access.
> > + * @is_write: Whether the access is write.
> > + *
> > + * Any DAMON API callers that notified access events can report the information
> > + * to DAMON using damon_report_access(). This struct contains the reporting
> > + * infomration. Refer to damon_report_access() for more details.
>
> nit: typo s/infomration/information/
As Akinobu kindly commented above, this change is borrowed from my tree, and
these typos also came from there. Thank you for catching these, Ian! I fixed
these in my tree.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-10 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 1:00 [RFC PATCH v2 0/6] mm/damon: introduce perf event based access check Akinobu Mita
2026-03-09 1:00 ` [RFC PATCH v2 1/6] mm/damon: reintroduce damon_operations->cleanup() Akinobu Mita
2026-03-09 1:00 ` [RFC PATCH v2 2/6] mm/damon/core: introduce struct damon_access_report Akinobu Mita
2026-03-09 15:19 ` Ian Rogers
2026-03-10 1:23 ` SeongJae Park [this message]
2026-03-09 1:00 ` [RFC PATCH v2 3/6] mm/damon/core: add common code for perf event based access check Akinobu Mita
2026-03-09 1:00 ` [RFC PATCH v2 4/6] mm/damon/vaddr: support " Akinobu Mita
2026-03-09 1:00 ` [RFC PATCH v2 5/6] mm/damon/paddr: " Akinobu Mita
2026-03-09 1:00 ` [RFC PATCH v2 6/6] mm/damon: allow user to set min size of region Akinobu Mita
2026-03-11 0:51 ` [RFC PATCH v2 0/6] mm/damon: introduce perf event based access check SeongJae Park
2026-03-13 7:35 ` Akinobu Mita
2026-03-14 1:31 ` SeongJae Park
2026-03-16 4:42 ` Akinobu Mita
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=20260310012329.93272-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akinobu.mita@gmail.com \
--cc=damon@lists.linux.dev \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.