From: Steven Rostedt <rostedt@goodmis.org>
To: "Yang Jialong 杨佳龙" <jialong.yang@shingroup.cn>
Cc: mhiramat@kernel.org, Karol Herbst <karolherbst@gmail.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
mathieu.desnoyers@efficios.com,
Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] powerpc/mmiotrace: Add MMIO Tracing tool for PowerPC
Date: Wed, 3 Jul 2024 17:41:29 -0400 [thread overview]
Message-ID: <20240703174129.7e19a9a6@rorschach.local.home> (raw)
In-Reply-To: <5F5B4CCA07D939BE+1a8b7985-b0c6-4b03-8c31-d1281f7b56e4@shingroup.cn>
On Wed, 3 Jul 2024 15:39:09 +0800
Yang Jialong 杨佳龙 <jialong.yang@shingroup.cn> wrote:
> Hello, mmiotrace maintainers.
>
> Here is a first version patch used to support mmiotrace function on
> powerpc platform. When I copy mmiotrace to powerpc archtecture, we found
> that there are many code are general, such as code in kmmio.c and
> mmio-mod.c in arch/x86/mm/. But we have file trace_mmiotrace.c as a low
> layer to finish the function. Whether we can abstract out one layer
> again or not?
>
The mmiotracer is at a minimal maintenance level. I constantly test it
and make sure it works (on x86) for every pull request I do. But I
haven't done much more than that.
If I ever got the time, I was going to make it work for SMP machines,
as it currently still requires running in UP (does a CPU hotplug to
shutdown all CPUs but one when enabled). But that's just because there
was no effort to make it multiprocessor safe. It is definitely doable.
But it is very low priority in my TODO list. I have no problem if you
want to clean it up and pull out the more generic parts. Hey, if you
have time, make it SMP safe if you can ;-) Although that may remove
one of my biggest bug finders. You'd be amazed at what breaks when you
aggressively disable all but one CPU and then enable all of them back
up again.
-- Steve
next prev parent reply other threads:[~2024-07-03 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 8:51 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
2024-06-28 8:21 ` Yang Jialong 杨佳龙
2024-07-03 7:39 ` Fwd: " Yang Jialong 杨佳龙
2024-07-03 21:41 ` Steven Rostedt [this message]
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=20240703174129.7e19a9a6@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=jialong.yang@shingroup.cn \
--cc=karolherbst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=ppaalanen@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
all inboxes | Powered by JetHome®