diff options
| author | Daniel Vetter <[email protected]> | 2020-02-04 16:01:45 +0100 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2020-02-11 15:03:09 +0100 |
| commit | 591a2abf149f6fa14807992eca60c9ee359f114d (patch) | |
| tree | cb41b20f2ac22b7f3a713004753c145b0a808e9a /tools/perf/scripts/python | |
| parent | c368ec194dd0e86e7516bc61ae1df584dec73e90 (diff) | |
drm: Push drm_global_mutex locking in drm_open
We want to only take the BKL on crap drivers, but to know whether
we have a crap driver we first need to look it up. Split this shuffle
out from the main BKL-disabling patch, for more clarity. Historical
aside: When the kernel-wide BKL was removed, it was replaced by
drm_global_mutex within the scope of the drm subsystem hence why these
two things are (almost) interchangeable as concepts here.
Since the minors are refcounted drm_minor_acquire is purely internal
and this does not have a driver visible effect.
v2: Push the locking even further into drm_open(), suggested by Chris.
This gives us more symmetry with drm_release(), and maybe a futuer
avenue where we make drm_global_mutex locking (partially) opt-in like
with drm_release_noglobal().
v3:
- Actually push this stuff correctly, don't unlock twice (Chris)
- Fix typo on commit message, plus explain why BKL = drm_global_mutex
(Sam)
Cc: Sam Ravnborg <[email protected]>
Cc: Chris Wilson <[email protected]>
Tested-by: Thomas Zimmermann <[email protected]>
Acked-by: Thomas Zimmermann <[email protected]>
Reviewed-by: Chris Wilson <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions