From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Javi Merino <javi.merino@kernel.org>
Subject: [for-next][PATCH 6/7] tracing, thermal: Hide devfreq trace events when not in use
Date: Wed, 18 Oct 2017 09:28:13 -0400 [thread overview]
Message-ID: <20171018132838.557217934@goodmis.org> (raw)
In-Reply-To: 20171018132807.255017131@goodmis.org
[-- Attachment #1: 0006-tracing-thermal-Hide-devfreq-trace-events-when-not-i.patch --]
[-- Type: text/plain, Size: 1374 bytes --]
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
As trace events when defined create data structures and functions to
process them, defining trace events when not using them is a waste of
memory.
The trace events thermal_power_devfreq_get_power and
thermal_power_devfreq_limit are only used when CONFIG_DEVFREQ_THERMAL
is set. Make those events only defined when that is set as well.
Link: http://lkml.kernel.org/r/20171013102150.0050cb74@gandalf.local.home
Acked-by: Javi Merino <javi.merino@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
include/trace/events/thermal.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/trace/events/thermal.h b/include/trace/events/thermal.h
index 6cde5b3514c2..1fdacdb94e77 100644
--- a/include/trace/events/thermal.h
+++ b/include/trace/events/thermal.h
@@ -148,6 +148,7 @@ TRACE_EVENT(thermal_power_cpu_limit,
__entry->power)
);
+#ifdef CONFIG_DEVFREQ_THERMAL
TRACE_EVENT(thermal_power_devfreq_get_power,
TP_PROTO(struct thermal_cooling_device *cdev,
struct devfreq_dev_status *status, unsigned long freq,
@@ -203,6 +204,7 @@ TRACE_EVENT(thermal_power_devfreq_limit,
__get_str(type), __entry->freq, __entry->cdev_state,
__entry->power)
);
+#endif /* CONFIG_DEVFREQ_THERMAL */
#endif /* _TRACE_THERMAL_H */
/* This part must be outside protection */
--
2.13.2
next prev parent reply other threads:[~2017-10-18 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 13:28 [for-next][PATCH 0/7] tracing: Some more updates for 4.15 Steven Rostedt
2017-10-18 13:28 ` [for-next][PATCH 2/7] perf/ftrace: Revert ("perf/ftrace: Fix double traces of perf on ftrace:function") Steven Rostedt
2017-10-18 13:28 ` [for-next][PATCH 3/7] perf/ftrace: Fix function trace events Steven Rostedt
2017-10-18 13:28 ` [for-next][PATCH 4/7] perf/ftrace: Small cleanup Steven Rostedt
2017-10-18 13:28 ` [for-next][PATCH 5/7] ftrace: Kill FTRACE_OPS_FL_PER_CPU Steven Rostedt
2017-10-18 13:28 ` Steven Rostedt [this message]
2017-10-18 13:28 ` [for-next][PATCH 7/7] tracing, thermal: Hide cpu cooling trace events when not in use Steven Rostedt
[not found] ` <20171018132837.670484526@goodmis.org>
2017-10-18 15:43 ` [for-next][PATCH 1/7] tracing, dma-buf: Remove unused trace event dma_fence_annotate_wait_on 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=20171018132838.557217934@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=javi.merino@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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