[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250612095828.6d75dfa3@batman.local.home>
Date: Thu, 12 Jun 2025 09:58:28 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: LKML <linux-kernel@...r.kernel.org>, Linux trace kernel
<linux-trace-kernel@...r.kernel.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>
Subject: [PATCH] alarmtimer: Hide alarmtimer_suspend event when RTC_CLASS is
not configured
From: Steven Rostedt <rostedt@...dmis.org>
The trace event alarmtimer_suspend is only called when RTC_CLASS is not
defined. As every event created can create up to 5K of text and meta data
regardless if it is called or not it should not be created and waste
memory. Hide the event when CONFIG_RTC_CLASS is not defined.
Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org>
---
Note, I will be adding code soon that will make unused events cause a warning.
include/trace/events/alarmtimer.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/trace/events/alarmtimer.h b/include/trace/events/alarmtimer.h
index 13483c7ca70b..8e9c76a7f21b 100644
--- a/include/trace/events/alarmtimer.h
+++ b/include/trace/events/alarmtimer.h
@@ -20,6 +20,7 @@ TRACE_DEFINE_ENUM(ALARM_BOOTTIME_FREEZER);
{ 1 << ALARM_REALTIME_FREEZER, "REALTIME Freezer" }, \
{ 1 << ALARM_BOOTTIME_FREEZER, "BOOTTIME Freezer" })
+#ifdef CONFIG_RTC_CLASS
TRACE_EVENT(alarmtimer_suspend,
TP_PROTO(ktime_t expires, int flag),
@@ -41,6 +42,7 @@ TRACE_EVENT(alarmtimer_suspend,
__entry->expires
)
);
+#endif /* CONFIG_RTC_CLASS */
DECLARE_EVENT_CLASS(alarm_class,
--
2.47.2
Powered by blists - more mailing lists