[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140107133111.0fe49c21@gandalf.local.home>
Date: Tue, 7 Jan 2014 13:31:11 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Dave Martin <Dave.Martin@....com>
Cc: Arnd Bergmann <arnd@...db.de>,
Russell King - ARM Linux <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
sahara <keun-o.park@...driver.com>,
Keun-O Park <kpark3469@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 19/19] [INCOMPLETE] ARM: make return_address available
for ARM_UNWIND
On Tue, 7 Jan 2014 16:36:29 +0000
Dave Martin <Dave.Martin@....com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists