Re: [git pull] tracing fixes

[Steven Rostedt]

On Thu, 17 Jul 2008, Ingo Molnar wrote:
>
> Ingo Molnar (4):
>       ftrace: fix merge buglet
>       ftrace: fix lockup with MAXSMP
>       ftrace: do not trace scheduler functions
>       ftrace: do not trace library functions
>

[...]
> --- a/kernel/Makefile
> +++ b/kernel/Makefile
> @@ -11,8 +11,6 @@ obj-y     = sched.o fork.o exec_domain.o panic.o printk.o profile.o \
>  	    hrtimer.o rwsem.o nsproxy.o srcu.o semaphore.o \
>  	    notifier.o ksysfs.o pm_qos_params.o sched_clock.o
>
> -CFLAGS_REMOVE_sched.o = -mno-spe
> -
>  ifdef CONFIG_FTRACE
>  # Do not trace debug files and internal ftrace files
>  CFLAGS_REMOVE_lockdep.o = -pg
> @@ -21,6 +19,7 @@ CFLAGS_REMOVE_mutex-debug.o = -pg
>  CFLAGS_REMOVE_rtmutex-debug.o = -pg
>  CFLAGS_REMOVE_cgroup-debug.o = -pg
>  CFLAGS_REMOVE_sched_clock.o = -pg
> +CFLAGS_REMOVE_sched.o = -mno-spe -pg
>  endif
>

Ingo,

Why not trace the scheduler functions? I found a lot of useful information
from seeing what functions are being called (namely the latencies caused
by the fair scheduler balancing). Not being able to trace sched.c seems to
keep a lot of useful data from being accessed.

also, is the '-mno-spe' save when ftrace is not configured?

-- Steve

--
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/