On Tue, May 19, 2015 at 01:27:07PM +1000, Michael Ellerman wrote:
> On Mon, 2015-05-18 at 14:29 +0200, Jiri Kosina wrote:
> >
> > ftrace already handles recursion protection by itself (depending on the
> > per-ftrace-ops FTRACE_OPS_FL_RECURSION_SAFE flag).
>
> OK, so I wonder why that's not working for us?
IIRC a data access fault happens just before that flag is looked at ;-)
I'm now thinking about a hybrid solution: mark the most critical functions
"notrace", especially those directly involved with MMU loading, and add
a per-thread flag to catch the not-so-obvious cases.
Torsten
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
