Thread (18 messages) 18 messages, 5 authors, 2014-01-06

[PATCH 2/2] sched_clock: Disable seqlock lockdep usage in sched_clock

From: Stephen Boyd <hidden>
Date: 2014-01-03 00:46:24
Also in: lkml

Possibly related (same subject, not in this thread)

On 01/02/14 15:11, John Stultz wrote:
Unforunately the seqlock lockdep enablmenet can't be used
s/Unforunately/Unfortunately/
s/enablmenet/enablement/
in sched_clock, since the lockdep infrastructure eventually
calls into sched_clock, which causes a deadlock.

Thus, this patch changes all generic sched_clock usage
to use the raw_* methods.

Cc: Krzysztof Ha?asa <khalasa@piap.pl>
Cc: Uwe Kleine-K?nig <redacted>
Cc: Willy Tarreau <w@1wt.eu>
Cc: Ingo Molnar <mingo@kernel.org>,
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephen Boyd <redacted>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arm-kernel at lists.infradead.org
Reported-by: Krzysztof Ha?asa <khalasa@piap.pl>
Signed-off-by: John Stultz <redacted>
Reviewed-by: Stephen Boyd <redacted>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help