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

2014-01-02 Thread Krzysztof Hałasa
John Stultz writes: > Unforunately the seqlock lockdep enablmenet can't be used > 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. These two patche

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

2014-01-02 Thread Stephen Boyd
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 al

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

2014-01-02 Thread John Stultz
Unforunately the seqlock lockdep enablmenet can't be used 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 Cc: Uwe Kleine-König Cc: W