[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250412221847.17310-1-iii@linux.ibm.com>
Date: Sun, 13 Apr 2025 00:10:42 +0200
From: Ilya Leoshkevich <iii@...ux.ibm.com>
To: Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Sven Schnelle <svens@...ux.ibm.com>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Heiko Carstens <hca@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Ilya Leoshkevich <iii@...ux.ibm.com>
Subject: [PATCH v2 0/2] ftrace: Expose call graph depth as unsigned int
v1: https://lore.kernel.org/lkml/20250411172207.61332-1-iii@linux.ibm.com/
v1 -> v2: Use unsigned int instead of int.
Add a follow-up patch that changes depth to unsigned int in
all events.
Hi,
This series changes the type of depth in all call graph events to
unsigned int.
Patch 1 fixes a size mismatch issue in ftrace_graph_ent_entry, which
causes trace-cmd on 64-bit big-endian systems to output a lot of bogus
spaces, rendering it unusable.
Patch 2 changes type of depth in all other events to unsigned int in
order to better reflect its semantics: it can only be negative
internally, but recorded values are always non-negative.
Best regards,
Ilya
Ilya Leoshkevich (2):
ftrace: Fix type of ftrace_graph_ent_entry.depth
ftrace: Expose call graph depth as unsigned int
kernel/trace/trace_entries.h | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
--
2.49.0
Powered by blists - more mailing lists