diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2019-08-15 21:57:08 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2019-08-15 23:21:13 +0100 |
commit | ccb23d2dcc300d3fa176de654610ea82f635915d (patch) | |
tree | c77c3f9c88b5960c5961ecd379d9f9682be2ad6a /drivers/gpu/drm/i915/display/intel_frontbuffer.h | |
parent | 338aade97c061da0403dbb00128d938782f30dbd (diff) | |
download | linux-ccb23d2dcc300d3fa176de654610ea82f635915d.tar.gz linux-ccb23d2dcc300d3fa176de654610ea82f635915d.tar.bz2 linux-ccb23d2dcc300d3fa176de654610ea82f635915d.zip |
drm/i915/gt: Guard timeline pinning without relying on struct_mutex
In preparation for removing struct_mutex from around context retirement,
we need to make timeline pinning and unpinning safe. Since multiple
engines/contexts can share a single timeline, we cannot rely on
borrowing the context mutex (otherwise we could state that the timeline
is only pinned/unpinned inside the context pin/unpin and so guarded by
it). However, we only perform a sequence of atomic operations inside the
timeline pin/unpin and the sequence of those operations is safe for a
concurrent unpin / pin, so we can relax the struct_mutex requirement.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190815205709.24285-3-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/display/intel_frontbuffer.h')
0 files changed, 0 insertions, 0 deletions