Re: [patch] latency tracer, 2.6.15-rc7

[Dave Jones]

On Thu, Dec 29, 2005 at 09:22:17AM +0100, Ingo Molnar wrote:
 > 
 > * Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
 > 
 > > I'm not sure how much work it would be to break out 
 > > CONFIG_LATENCY_TRACE as a separate patch.
 > 
 > could you check out the 2.6.15-rc7 version of the latency tracer i 
 > uploaded to:
 > 
 > 	http://redhat.com/~mingo/latency-tracing-patches/
 > 
 > could test it by e.g. trying to reproduce the same VM latency as in the 
 > -rt tree. [the two zlib patches are needed if you are using 4K stacks, 
 > mcount increases stack footprint.]

kernel/latency.c: In function 'add_preempt_count_ti':
kernel/latency.c:1703: warning: implicit declaration of function 'preempt_count_ti'
kernel/latency.c:1703: error: invalid lvalue in assignment
kernel/latency.c: In function 'sub_preempt_count_ti':
kernel/latency.c:1764: error: invalid lvalue in assignment

interesting config options ...

# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y

CONFIG_WAKEUP_TIMING=y
CONFIG_WAKEUP_LATENCY_HIST=y
CONFIG_CRITICAL_IRQSOFF_TIMING=y
CONFIG_INTERRUPT_OFF_HIST=y
CONFIG_LATENCY_TRACE=y
CONFIG_USE_FRAME_POINTER=y
CONFIG_FRAME_POINTER=y

		Dave

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