From: Michael Ellerman <mpe@ellerman.id.au>
To: Jialong Yang <jialong.yang@shingroup.cn>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
Cc: luming.yu@shingroup.cn, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Karol Herbst <karolherbst@gmail.com>,
shenghui.qu@shingroup.cn, Pekka Paalanen <ppaalanen@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linuxppc-dev@lists.ozlabs.org,
Jialong Yang <jialong.yang@shingroup.cn>
Subject: Re: [PATCH v1 1/2] powerpc/mmiotrace: Add MMIO Tracing tool for PowerPC
Date: Fri, 28 Jun 2024 17:02:48 +1000 [thread overview]
Message-ID: <87h6ddlfc7.fsf@mail.lhotse> (raw)
In-Reply-To: <2bf90acf7d29641ba6643934ff8dbba897dbd2d9.1718873074.git.jialong.yang@shingroup.cn>
Jialong Yang <jialong.yang@shingroup.cn> writes:
> mmiotrace is a useful tool to trace MMIO accesses. Nowadays, it only
> supported on x86 and x86_64 platforms.
I've never used mmiotrace, and don't know it well.
I'm not necessarily opposed to merging it, but AFAIK it was mostly used
for reverse engineering proprietary drivers, where the driver itself
couldn't be easily instrumented. Is that what you're using it for?
For drivers where we have the source wouldn't it be easier to just use
tracepoints in the MMIO accessors?
Is it still in-use/maintained on the x86 side?
> Here is a support for powerpc.
> The manual is located at Documentation/trace/mmiotrace.rst which means
> I have not changed user API. People will be easy to use it.
> Almost all files are copied from x86/mm, there are only some
> differences from hardware and architectures software.
>
> LINK: https://lore.kernel.org/lkml/20080127195536.50809974@daedalus.pq.iki.fi/
>
> Signed-off-by: Jialong Yang <jialong.yang@shingroup.cn>
> ---
> arch/powerpc/Kconfig.debug | 3 +
> arch/powerpc/mm/Makefile | 1 +
> arch/powerpc/mm/kmmio.c | 649 +++++++++++++++++++++++++++++++
> arch/powerpc/mm/mmio-mod.c | 414 ++++++++++++++++++++
> arch/powerpc/mm/mmiotrace_arch.c | 149 +++++++
> arch/powerpc/mm/mmiotrace_arch.h | 25 ++
> arch/powerpc/mm/pf_in.c | 185 +++++++++
> arch/powerpc/mm/pf_in.h | 33 ++
> 8 files changed, 1459 insertions(+)
At a glance most of that code could be shared between arches. I don't
think I can merge that as-is, without some attempt to split the generic
parts out.
cheers
next prev parent reply other threads:[~2024-06-28 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 8:51 [PATCH v1 1/2] powerpc/mmiotrace: Add MMIO Tracing tool for PowerPC Jialong Yang
2024-06-20 8:51 ` [PATCH v1 2/2] powerpc/mmiotrace: bind ioremap and page fault to active mmiotrace Jialong Yang
2024-06-27 12:31 ` [PATCH v1 1/2] powerpc/mmiotrace: Add MMIO Tracing tool for PowerPC kernel test robot
2024-06-28 7:02 ` Michael Ellerman [this message]
2024-06-28 8:21 ` Yang Jialong 杨佳龙
2024-09-04 7:47 ` 虞陆铭
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=87h6ddlfc7.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=jialong.yang@shingroup.cn \
--cc=karolherbst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luming.yu@shingroup.cn \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=nouveau@lists.freedesktop.org \
--cc=npiggin@gmail.com \
--cc=ppaalanen@gmail.com \
--cc=rostedt@goodmis.org \
--cc=shenghui.qu@shingroup.cn \
/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;
as well as URLs for NNTP newsgroup(s).