linux-toradex.git/kernel/trace/trace_irqsoff.c, branch v2.6.27.7

ftrace: fix modular build

2008-07-26T13:08:22+00:00

fix:

 ERROR: "start_critical_timings" [drivers/acpi/processor.ko] undefined!
 ERROR: "stop_critical_timings" [drivers/acpi/processor.ko] undefined!

Signed-off-by: Ingo Molnar

ftrace: only trace preempt off with preempt tracer

2008-07-18T16:57:34+00:00

When PREEMPT_TRACER and IRQSOFF_TRACER are both configured and irqsoff
tracer is running, the preempt_off sections might also be traced.

Thanks to Andrew Morton for pointing out my mistake of spin_lock disabling
interrupts while he was reviewing ftrace.txt. Seems that my example I used
actually hit this bug.

Signed-off-by: Steven Rostedt 
Cc: Linus Torvalds 
Cc: Andrew Morton 
Cc: Peter Zijlstra 
Signed-off-by: Ingo Molnar

ftrace: remove printks from irqsoff trace

2008-05-26T20:51:27+00:00

Printing out new max latencies was fine for the old RT tracer. But for
mainline it is a bit messy. We also need to test if the run queue
is locked before we can do the print. This means that we may not be
printing out latencies if the run queue is locked on another CPU.
This produces inconsistencies in the output.

This patch simply removes the print altogether.

Signed-off-by: Steven Rostedt 
Cc: pq@iki.fi
Cc: proski@gnu.org
Cc: sandmann@redhat.com
Cc: a.p.zijlstra@chello.nl
Signed-off-by: Thomas Gleixner

ftrace: irqsoff use raw_smp_processor_id

2008-05-23T19:13:41+00:00

This patch changes the use of __get_cpu_var to explicitly calling
raw_smp_processor_id and using the per_cpu() macro. On some debug
configurations, the use of __get_cpu_var may cause ftrace to trigger
and this can cause problems with the irqsoff tracing.

Signed-off-by: Steven Rostedt 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

ftrace: printk and trace irqsoff and wakeups

2008-05-23T19:13:02+00:00

printk called from wakeup critical timings and irqs off can
cause deadlocks since printk might do a wakeup itself. If the
call to printk happens with the runqueue lock held, it can
deadlock.

This patch protects the printk from being called in trace irqs off
with a test to see if the runqueue for the current CPU is locked.
If it is locked, the printk is skipped.

The wakeup always holds the runqueue lock, so the printk is
simply removed.

Signed-off-by: Steven Rostedt 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

ftrace: remove notrace

2008-05-23T18:58:28+00:00

now that we have a kbuild method for notrace, no need to pollute the
C code with the annotations.

Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

ftrace: cleanups

2008-05-23T18:56:05+00:00

clean up recent code.

Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

ftrace: add trace_function api for other tracers to use

2008-05-23T18:55:55+00:00

A new check was added in the ftrace function that wont trace if the CPU
trace buffer is disabled.  Unfortunately, other tracers used ftrace() to
write to the buffer after they disabled it. The new disable check makes
these calls into a nop.

This patch changes the __ftrace that is called without the check into a
new api for the other tracers to use, called "trace_function". The other
tracers use this interface instead when the trace CPU buffer is already
disabled.

Signed-off-by: Steven Rostedt 
Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

ftrace: timestamp syncing, prepare

2008-05-23T18:42:31+00:00

rename and uninline now() to ftrace_now().

Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

ftrace: cleanups

2008-05-23T18:40:46+00:00

factor out code and clean it up.

Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner