From: Akinobu Mita <akinobu.mita@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon: trace: print address range in hex
Date: Tue, 31 Dec 2024 21:56:43 +0900 [thread overview]
Message-ID: <CAC5umyh9k_xvRws9HdmuF8op424VL8j50304+m=GsY+jfxADbQ@mail.gmail.com> (raw)
In-Reply-To: <20241230183909.14559-1-sj@kernel.org>
2024年12月31日(火) 3:39 SeongJae Park <sj@kernel.org>:
>
> On Mon, 30 Dec 2024 10:28:13 -0800 SeongJae Park <sj@kernel.org> wrote:
>
> > Hello Akinobu,
> >
> > On Mon, 30 Dec 2024 22:42:20 +0900 Akinobu Mita <akinobu.mita@gmail.com> wrote:
> >
> > > Currently, the address ranges are displayed in decimal format in
> > > tracepoints for DAMON, but hexadecimal format is easier to compare with
> > > address ranges in /proc/<pid>/numa_maps.
> >
> > I agree that it could be easier for the use case. But, I think writing and
> > using a script converting formats for DAMON tracepoint output or numa_maps
> > could also be a way to resolve the issue.
>
> For example, we can extend 'damo' to optionally do the conversion. Depending
> on your use case (if you also use 'damo' for your use case), it might be a way
> to move forward?
I'm currently using perf trace (-e damon:* --libtraceevent_print) to see which
address range accesses were detected or not, so as you suggested, I'll create a
script to convert the output of the perf trace.
next prev parent reply other threads:[~2024-12-31 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 13:42 Akinobu Mita
2024-12-30 13:42 ` [PATCH damo] _damo_records: support address range in hex format Akinobu Mita
2024-12-30 18:35 ` SeongJae Park
2024-12-30 18:28 ` [PATCH] mm/damon: trace: print address range in hex SeongJae Park
2024-12-30 18:39 ` SeongJae Park
2024-12-31 12:56 ` Akinobu Mita [this message]
2025-01-01 17:43 ` 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='CAC5umyh9k_xvRws9HdmuF8op424VL8j50304+m=GsY+jfxADbQ@mail.gmail.com' \
--to=akinobu.mita@gmail.com \
--cc=damon@lists.linux.dev \
--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