| commit | f52be5708076b75a045ac52c6fef3fffb8300525 | [log] [tgz] |
|---|---|---|
| author | Peter Zijlstra <[email protected]> | Tue Aug 29 10:59:39 2017 +0200 |
| committer | Ingo Molnar <[email protected]> | Tue Aug 29 15:14:38 2017 +0200 |
| tree | 8e98d8731a45427562e9429a2e763e74828acc27 | |
| parent | 7b3d61cc73a1abe4c2c7eaf00093b338c8b233b0 [diff] |
locking/lockdep: Untangle xhlock history save/restore from task independence
Where XHLOCK_{SOFT,HARD} are save/restore points in the xhlocks[] to
ensure the temporal IRQ events don't interact with task state, the
XHLOCK_PROC is a fundament different beast that just happens to share
the interface.
The purpose of XHLOCK_PROC is to annotate independent execution inside
one task. For example workqueues, each work should appear to run in its
own 'pristine' 'task'.
Remove XHLOCK_PROC in favour of its own interface to avoid confusion.
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Byungchul Park <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>