On Tue, 29 Sep 2015, Peter Zijlstra wrote: > preempt_schedule_common() is marked notrace, but it does not use > _notrace() preempt_count functions and __schedule() is also not marked > notrace, which means that its perfectly possible to end up in the > tracer from preempt_schedule_common(). > > So either we need more notrace, or we need to remove notrace from > preempt_schedule_common().
More notrace is the right thing to do. We have enough pointless information in tracing already. Reviewed-by: Thomas Gleixner <t...@linutronix.de> -- 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/
