Thread (12 messages) 12 messages, 6 authors, 2014-01-07

[PATCH 19/19] [INCOMPLETE] ARM: make return_address available for ARM_UNWIND

From: rostedt@goodmis.org (Steven Rostedt)
Date: 2014-01-07 18:31:22
Also in: lkml

Possibly related (same subject, not in this thread)

On Tue, 7 Jan 2014 16:36:29 +0000
Dave Martin [off-list ref] wrote:
My other concern was that we might end up in a recursive trace due to
the use of non-notrace core functions in the unwinder.  But I seem to
remember Steve Rostedt saying the the tracer guards against recursive
invocation nowadays -- if so, that shouldn't be a problem.
I guess it matters what type of tracing you are talking about. The
function tracer protects against all recursive contexts (normal,
softirq, irq and NMI) and so does the ring buffer (same levels).

Those may be the only ones that matter, as things like events shouldn't
recurse, unless you have an event in the unwinder itself. But that's
where you take the doctor's advice of "don't do that".

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help