Re: [RFC][PATCH] Make ftrace able to trace function return

[Frédéric Weisbecker]

2008/10/30 Steven Rostedt <rostedt@xxxxxxxxxxx>:
> What about storing the return addresses on the bottom of the stack?
> That is, start at task->stack + sizeof(thread_info), and stack up on that.
> Be careful, there might already be users of that area. This will also need
> to be arch dependent.

But how could I assume there is enough space behind this address to store a long
stack of functions calls for a same thread?
And if an interrupt is raised, would a reference to "current task" be
really consistant?

I don't know much about the bottom stack of the tasks, I'm not sure
about how much
space I can use inside... I should study this field. Who could be the
potential users of this area?
--
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/