aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts.py
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2015-10-10 10:44:32 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2015-10-13 13:08:43 +0200
commit6042639c4c7f9e8a0c634245f034eb94827591a8 (patch)
tree463da7e0403c102da2e1ec96e3e5b9aa86ea22b0 /tools/perf/scripts/python/syscall-counts.py
parent115719fceaa733d646e39cdce83cc32ddb891a49 (diff)
drm/i915: Hold dev->event_lock whilst inspecting intel_crtc->unpin_work
We should serialise access to the intel_crtc->unpin_work through the dev->event_lock spinlock. It should not be possible for it to disappear without severe error as the mmio_flip worker has not tagged the unpin_work pending flip-completion. Similarly if the error exists, just taking the unpin_work whilst holding the spinlock and then using it unserialised just masks the race. (It is supposed to be valid as the unpin_work exists until the flip completion interrupt which should not fire until we flush the mmio writes to update the display base which is the last time we access the unpin_work from the kthread.) References: https://bugs.freedesktop.org/show_bug.cgi?id=92335 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions