Thread (39 messages) 39 messages, 7 authors, 2009-02-16

Re: [PATCH 3/3] tracing: Tracers that use CALLER_ADDR macros should select FRAME_POINTER

From: Anton Vorontsov <hidden>
Date: 2009-02-04 15:36:55
Also in: linux-rt-users, lkml

On Wed, Feb 04, 2009 at 04:26:15PM +0100, Frédéric Weisbecker wrote:
[...]
quoted
@@ -136,6 +138,7 @@ config SCHED_TRACER
       select TRACING
       select CONTEXT_SWITCH_TRACER
       select TRACER_MAX_TRACE
+       select FRAME_POINTER
       help
         This tracer tracks the latency of the highest priority task
         to be scheduled in, starting from the point it has woken up.
--

Looks right.

BTW, how behaves builtin_return_address in case of !FRAME_POINTERS ?
I guess it would only work with the first caller builtin_return_address(0)
It depends on the architecture. On PowerPC we always have frame pointers,
thus __builtin_return_address(1..) will always work. On x86 it won't work
that way.

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help