From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: [PATCH] libtraceevent: Add NEED_RESCHED_LAZY flag
Date: Wed, 2 Apr 2025 12:23:03 -0400 [thread overview]
Message-ID: <20250402122303.70ba14fa@gandalf.local.home> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
Starting with v6.13 the IRQS_NOSUPPORT latency flag was replaced by the
NEED_RSCHED_LAZY flag. Update the library to do the same.
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
include/traceevent/event-parse.h | 2 +-
src/event-parse.c | 6 ++----
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/include/traceevent/event-parse.h b/include/traceevent/event-parse.h
index 2b39b38..1a7984b 100644
--- a/include/traceevent/event-parse.h
+++ b/include/traceevent/event-parse.h
@@ -406,7 +406,7 @@ static inline int tep_is_bigendian(void)
/* taken from kernel/trace/trace.h */
enum trace_flag_type {
TRACE_FLAG_IRQS_OFF = 0x01,
- TRACE_FLAG_IRQS_NOSUPPORT = 0x02,
+ TRACE_FLAG_NEED_RESCHED_LAZY = 0x02,
TRACE_FLAG_NEED_RESCHED = 0x04,
TRACE_FLAG_HARDIRQ = 0x08,
TRACE_FLAG_SOFTIRQ = 0x10,
diff --git a/src/event-parse.c b/src/event-parse.c
index f2e50b0..dcaf27b 100644
--- a/src/event-parse.c
+++ b/src/event-parse.c
@@ -6809,11 +6809,9 @@ static void data_latency_format(struct tep_handle *tep, struct trace_seq *s,
softirq = lat_flags & TRACE_FLAG_SOFTIRQ;
trace_seq_printf(&sq, "%c%c%c",
- (lat_flags & TRACE_FLAG_IRQS_OFF) ? 'd' :
- (lat_flags & TRACE_FLAG_IRQS_NOSUPPORT) ?
- 'X' : '.',
+ (lat_flags & TRACE_FLAG_IRQS_OFF) ? 'd' : '.',
(lat_flags & TRACE_FLAG_NEED_RESCHED) ?
- 'N' : '.',
+ 'N' : (lat_flags & TRACE_FLAG_NEED_RESCHED_LAZY) ? 'L' :'.',
(hardirq && softirq) ? 'H' :
hardirq ? 'h' : softirq ? 's' : '.');
--
2.47.2
reply other threads:[~2025-04-02 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250402122303.70ba14fa@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.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;
as well as URLs for NNTP newsgroup(s).