From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/2] tracing: Fixes for 6.13
Date: Tue, 14 Jan 2025 09:53:13 -0500 [thread overview]
Message-ID: <20250114145313.452899098@goodmis.org> (raw)
Tracing fixes for 6.13:
- Fix a regression in the irqsoff and wakeup latency tracing
The function graph tracer infrastructure has become generic so that
kretprobes and BPF can be based on it. As it use to only handle
function graph tracing, it would always calculate the time the
function entered so that it could then calculate the time it exits
and give the length of time the function executed for. But this is
not needed for the other users (kretprobes and BPF) and the reading
the clock adds a non-negligible overhead, so the calculation was
moved into the function graph tracer logic.
But the irqsoff and wakeup latency tracers, when the "display-graph"
option was set, would use the function graph tracer to calculate the
times of functions during the latency. The movement of the calltime
calculation made the value zero for these tracers, and the output
no longer showed the length of time of each tracer, but instead the
absolute timestamp of when the function returned (rettime - calltime
where calltime is zero).
Have the irqsoff and wakeup latency tracers also do the calltime
calculation as the function graph tracer does.
- Update the tracing display to reflect the new preempt lazy model
When the system is configured with preempt lazy, the output of the
trace data would state "unknown" for the current preemption model.
Because the lazy preemption model was just added, make it known
to the tracing subsystem too.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes
Head SHA1: 24e0e610400aa2c765ee87b1b3c1401732b20fc5
Shrikanth Hegde (1):
tracing: Print lazy preemption model
Steven Rostedt (1):
tracing: Fix irqsoff and wakeup latency tracers when using function graph
----
kernel/trace/trace.c | 1 +
kernel/trace/trace_irqsoff.c | 14 ++++++++++++++
kernel/trace/trace_sched_wakeup.c | 14 ++++++++++++++
3 files changed, 29 insertions(+)
next reply other threads:[~2025-01-14 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 14:53 Steven Rostedt [this message]
2025-01-14 14:53 ` [for-linus][PATCH 1/2] tracing: Fix irqsoff and wakeup latency tracers when using function graph Steven Rostedt
2025-01-14 14:53 ` [for-linus][PATCH 2/2] tracing: Print lazy preemption model Steven Rostedt
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=20250114145313.452899098@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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