Re: [PATCH 1/2] tracing, thermal: Hide devfreq trace events when not in use

2017-10-17 Thread Javi Merino
On Fri, Oct 13, 2017 at 10:21:50AM -0400, Steven Rostedt wrote: > From: Steven Rostedt (VMware) > > 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

Re: [PATCH 1/2] tracing, thermal: Hide devfreq trace events when not in use

2017-10-17 Thread Javi Merino
On Fri, Oct 13, 2017 at 10:21:50AM -0400, Steven Rostedt wrote: > From: Steven Rostedt (VMware) > > 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

[PATCH 1/2] tracing, thermal: Hide devfreq trace events when not in use

2017-10-13 Thread Steven Rostedt
From: Steven Rostedt (VMware) 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

[PATCH 1/2] tracing, thermal: Hide devfreq trace events when not in use

2017-10-13 Thread Steven Rostedt
From: Steven Rostedt (VMware) 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