[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240613093233.0b349ed0@rorschach.local.home>
Date: Thu, 13 Jun 2024 09:32:33 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Andy Chiu <andy.chiu@...ive.com>
Cc: Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
<palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti
<alexghiti@...osinc.com>, Zong Li <zong.li@...ive.com>, Masami Hiramatsu
<mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>, Nathan
Chancellor <nathan@...nel.org>, Nick Desaulniers <ndesaulniers@...gle.com>,
Bill Wendling <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>,
Puranjay Mohan <puranjay@...nel.org>, Palmer Dabbelt <palmer@...osinc.com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH 2/8] tracing: do not trace kernel_text_address()
On Thu, 13 Jun 2024 15:11:07 +0800
Andy Chiu <andy.chiu@...ive.com> wrote:
> kernel_text_address() and __kernel_text_address() are called in
> arch_stack_walk() of riscv. This results in excess amount of un-related
> traces when the kernel is compiled with CONFIG_TRACE_IRQFLAGS. The
> situation worsens when function_graph is active, as it calls
> local_irq_save/restore in each function's entry/exit. This patch adds
> both functions to notrace, so they won't show up on the trace records.
I rather not add notrace just because something is noisy.
You can always just add:
echo '*kernel_text_address' > /sys/kernel/tracing/set_ftrace_notrace
and achieve the same result.
-- Steve
Powered by blists - more mailing lists