[PATCH 1/2] tracing/function-return-tracer: Make the function return tracer lockless

[PATCH 1/2] tracing/function-return-tracer: Make the function return tracer lockless

Post by Fric Weisb » Fri, 14 Nov 2008 18:20:11


2008/11/13 Ingo Molnar < XXXX@XXXXX.COM >:



But I guess this flag would apply on the timestamp inserted by the
ring-buffer. Unfortunately I can't use it
since I have to capture the clock for two times and not only during
insertion in the ring-buffer.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[PATCH 1/2] tracing/function-return-tracer: Make the function return tracer lockless

Post by Fric Weisb » Fri, 14 Nov 2008 18:30:11

2008/11/13 Ingo Molnar < XXXX@XXXXX.COM >:





If so that would be suitable. And for his purpose, the ring-buffer
would propose a function for time snapshot
adapted to the current flags and that rely on sched_clock?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/