Commit da89a7a2536c46e76a1a4351a70a8b8417e5fed1

Authored by Steven Rostedt
Committed by Thomas Gleixner
1 parent 7e18d8e701

ftrace: remove printks from irqsoff trace

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 <srostedt@redhat.com>
Cc: pq@iki.fi
Cc: proski@gnu.org
Cc: sandmann@redhat.com
Cc: a.p.zijlstra@chello.nl
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Showing 1 changed file with 0 additions and 16 deletions Side-by-side Diff

kernel/trace/trace_irqsoff.c
... ... @@ -165,22 +165,6 @@
165 165  
166 166 update_max_tr_single(tr, current, cpu);
167 167  
168   - if (!runqueue_is_locked()) {
169   - if (tracing_thresh) {
170   - printk(KERN_INFO "(%16s-%-5d|#%d): %lu us critical"
171   - " section violates %lu us threshold.\n",
172   - current->comm, current->pid,
173   - raw_smp_processor_id(),
174   - latency, nsecs_to_usecs(tracing_thresh));
175   - } else {
176   - printk(KERN_INFO "(%16s-%-5d|#%d): new %lu us"
177   - " maximum-latency critical section.\n",
178   - current->comm, current->pid,
179   - raw_smp_processor_id(),
180   - latency);
181   - }
182   - }
183   -
184 168 max_sequence++;
185 169  
186 170 out_unlock: