Files
kernel-tenderloin-3.0/kernel
Frederic Weisbecker f201ae2356 tracing/function-return-tracer: store return stack into task_struct and allocate it dynamically
Impact: use deeper function tracing depth safely

Some tests showed that function return tracing needed a more deeper depth
of function calls. But it could be unsafe to store these return addresses
to the stack.

So these arrays will now be allocated dynamically into task_struct of current
only when the tracer is activated.

Typical scheme when tracer is activated:
- allocate a return stack for each task in global list.
- fork: allocate the return stack for the newly created task
- exit: free return stack of current
- idle init: same as fork

I chose a default depth of 50. I don't have overruns anymore.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-11-23 09:17:26 +01:00
..
2008-10-22 07:37:17 +02:00
2008-10-16 11:21:30 -07:00
2008-09-14 16:25:35 +02:00
2008-11-19 18:49:58 -08:00
2008-07-28 14:37:38 +02:00
2008-08-13 12:55:10 +02:00
2008-10-28 11:19:07 +01:00
2008-09-02 19:21:40 -07:00
2008-11-19 10:19:16 +01:00
2008-10-20 08:52:39 -07:00
2008-10-21 15:59:53 +02:00
2008-11-18 15:08:56 +01:00
2008-11-11 11:57:22 +01:00
2008-11-05 10:30:14 +01:00
2008-11-06 08:41:56 +01:00
2008-10-16 11:21:31 -07:00
2008-11-19 18:49:57 -08:00
2008-07-25 10:53:45 -07:00
2008-11-04 13:04:40 +01:00
2008-10-16 11:21:47 -07:00
2008-10-16 11:21:31 -07:00