Re: [PATCH 06/18] sched: Generate trace points only if schedulertracing is enabled

[Frederic Weisbecker]

On Tue, Mar 23, 2010 at 01:32:08AM +0100, Jan Kara wrote:
> CC: Ingo Molnar <mingo@xxxxxxx>
> CC: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
> Signed-off-by: Jan Kara <jack@xxxxxxx>
> ---


Note this one is an exception.
Once tracing is enabled, we need the context switch
tracer anyway to keep track of the pid:cmdline mappings.



>  include/trace/events/sched.h |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
> index cfceb0b..0a08ab1 100644
> --- a/include/trace/events/sched.h
> +++ b/include/trace/events/sched.h
> @@ -1,5 +1,7 @@
>  #undef TRACE_SYSTEM
> +#undef TRACE_CONFIG
>  #define TRACE_SYSTEM sched
> +#define TRACE_CONFIG CONFIG_CONTEXT_SWITCH_TRACER
>  
>  #if !defined(_TRACE_SCHED_H) || defined(TRACE_HEADER_MULTI_READ)
>  #define _TRACE_SCHED_H
> -- 
> 1.6.4.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/