Jan Kiszka wrote:
Hi Philippe,
two minor updates I fixed since your last merge. The first one triggers
if the tracer tries to warn of debugging switch related latencies. The
second one when building very specific out-of-tree modules against the
kernel (here: madwifi with its binary-only component), stumbling over
-pg vs. -fomit-frame-pointer.
No need for a separate ipipe release from my POV, just apply for the
next round.
Ok, queued. Thanks.
Jan
------------------------------------------------------------------------
--- ./kernel/ipipe/tracer.c.orig 2006-01-07 13:28:01.000000000 +0100
+++ ./kernel/ipipe/tracer.c 2006-01-08 23:08:45.000000000 +0100
@@ -821,7 +821,7 @@ static void *__ipipe_frozen_prtrace_star
"------------------------------------------------------"
"------\n",
UTS_RELEASE, IPIPE_ARCH_STRING);
- __ipipe_print_dbgwarning();
+ __ipipe_print_dbgwarning(m);
seq_printf(m, "Freeze: %lld cycles, Trace Points: %d (+%d)\n\n",
print_path->point[print_path->begin].timestamp,
print_pre_trace+1, print_post_trace);
--- ./kernel/ipipe/Kconfig.orig 2006-01-07 13:28:01.000000000 +0100
+++ ./kernel/ipipe/Kconfig 2006-01-07 14:24:50.000000000 +0100
@@ -17,6 +17,7 @@ config IPIPE_STATS
config IPIPE_TRACE
bool "Latency Tracing"
depends on IPIPE && PROC_FS
+ select FRAME_POINTER
default n
---help---
Activate this option if you want to use per-function tracing of
--
Philippe.
