Ouch, what was I thinking for that initializing flags to zero:
Sorry, lets try that again:
Signed-off-by: Steven Rostedt
Index: linux_realtime_ernie/kernel/latency.c
===================================================================
--- linux_realtime_ernie/kernel/latency.c (revision 293)
+++ linux_realtime_ernie/kernel/latency.c (working copy)
@@ -1307,12 +1307,13 @@
T1 = cycles();
delta = T1-T0;
+ raw_local_save_flags(flags);
+
#ifndef CONFIG_CRITICAL_LATENCY_HIST
if (!report_latency(delta))
goto out;
#endif
- raw_local_save_flags(flags);
____trace(cpu, TRACE_FN, tr, CALLER_ADDR0, parent_eip, 0, 0, 0, flags);
/*
* Update the timestamp, because the trace entry above
@@ -1441,7 +1442,7 @@
_trace_cmdline(cpu, tr);
raw_local_save_flags(flags);
- ____trace(cpu, TRACE_FN, tr, eip, parent_eip, 0, 0, 0);
+ ____trace(cpu, TRACE_FN, tr, eip, parent_eip, 0, 0, 0, flags);
atomic_dec(&tr->disabled);
}
@@ -1459,7 +1460,7 @@
atomic_inc(&tr->disabled);
raw_local_save_flags(flags);
- ____trace(cpu, TRACE_FN, tr, eip, parent_eip, 0, 0, 0);
+ ____trace(cpu, TRACE_FN, tr, eip, parent_eip, 0, 0, 0, flags);
check_critical_timing(cpu, tr, eip);
tr->critical_start = 0;
atomic_dec(&tr->disabled);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|