Re: [RFC][PATCH 17/18 v2] ftrace/cpuidle/x86: Mark functions thatare RCU unsafe

From: H. Peter Anvin
Date: Tue Sep 03 2013 - 20:17:51 EST


On 08/30/2013 10:11 PM, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)" <rostedt@xxxxxxxxxxx>
>
> Some callbacks of the function tracer use rcu_read_lock(). This means that
> there's places that can not be traced because RCU is not tracking the CPU
> for various reasons (like NO_HZ_FULL and coming back from userspace).
>
> Thes functions need to be marked so that callbacks that use RCU do not
> trace them.
>
> Cc: H. Peter Anvin <hpa@xxxxxxxxx>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
> Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>

Acked-by: H. Peter Anvin <hpa@xxxxxxxxx>

--
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/