From: Steven Rostedt <rostedt@goodmis.org>
To: Roman 'Hedin' Storozhenko <romeusmeister@gmail.com>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: mm: Trace TLB flush path selection
Date: Sat, 29 Aug 2026 21:22:02 -0400 [thread overview]
Message-ID: <20260829212202.57db49ca@robin> (raw)
In-Reply-To: <20260829-tlb_tracepoint-v1-1-dfdaede7e741@gmail.com>
On Sat, 29 Aug 2026 17:44:18 +0200
Roman 'Hedin' Storozhenko <romeusmeister@gmail.com> wrote:
> +static __always_inline void
> +riscv_tlb_trace_flush_path(const struct cpumask *cmask, unsigned long start,
> + unsigned long size, unsigned long stride,
> + unsigned long asid, bool has_mm,
> + enum riscv_tlb_flush_path path)
> +{
> + enum riscv_tlb_flush_scope scope;
> +
> + if (!trace_riscv_tlb_flush_path_enabled())
> + return;
> +
> + scope = riscv_tlb_get_flush_scope(size, stride, has_mm);
> + trace_riscv_tlb_flush_path(start, size, stride, asid, has_mm, cmask,
> + scope, path);
instead of using two static calls you can use the new:
trace_call__riscv_tlb_flush_path()
That is to be used instead of the trace_<event>() if it's behind a
trace_<event>_enabled() check. That is because the
trace_call__<event>() will always trigger the trace event logic because
it should only be called when the trace event was enabled.
-- Steve
> +}
> +
next prev parent reply other threads:[~2026-08-30 1:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 15:44 Roman 'Hedin' Storozhenko
2026-08-30 1:22 ` Steven Rostedt [this message]
2026-08-30 14:19 ` Roman Storozhenko
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=20260829212202.57db49ca@robin \
--to=rostedt@goodmis.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=romeusmeister@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®