diff options
| author | Daniel Vetter <[email protected]> | 2019-11-20 11:56:07 +0100 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2019-11-21 11:03:31 +0100 |
| commit | 92ec07677107974c31b32030a4f897398e452ca9 (patch) | |
| tree | c820e36349d08240f22e3afa6ecf67f761a0c1aa /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | fedf7a441fe89d17907218f6cd53975a9a929837 (diff) | |
drm/msm: Don't init ww_mutec acquire ctx before needed
For locking semantics it really doesn't matter when we grab the
ticket. But for lockdep validation it does: the acquire ctx is a fake
lockdep. Since other drivers might want to do a full multi-lock dance
in their fault-handler, not just lock a single dma_resv. Therefore we
must init the acquire_ctx only after we've done all the copy_*_user or
anything else that might trigger a pagefault. For msm this means we
need to move it past submit_lookup_objects.
Aside: Why is msm still using struct_mutex, it seems to be using
dma_resv_lock for general buffer state protection?
v2:
- Add comment to explain why the ww ticket setup is separate (Rob)
- Fix up error handling, we need to make sure we don't call
ww_acquire_fini without _init.
Reviewed-by: Maarten Lankhorst <[email protected]>
Reviewed-and-tested-by: Rob Clark <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Cc: Rob Clark <[email protected]>
Cc: Sean Paul <[email protected]>
Cc: [email protected]
Cc: [email protected]
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions