]> asedeno.scripts.mit.edu Git - linux.git/commit
drm/i915: Drop assertion that ce->pin_mutex guards state updates
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 22 Oct 2019 12:28:45 +0000 (13:28 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Tue, 22 Oct 2019 12:32:01 +0000 (13:32 +0100)
commit0587152bf9a0d7ebfd7fcb401068a742027adb2a
treec388c2307d1e3769e0a6c3bb82b477ff9f4beb1c
parente948761f5b024284dc423172e9aca0672f3dec5b
drm/i915: Drop assertion that ce->pin_mutex guards state updates

The actual conditions are that we know the GPU is not accessing the
context, and we hold a pin on the context image to allow CPU access. We
used a fake lock on ce->pin_mutex so that we could try and use lockdep
to assert that access is serialised, but the various different
hardirq/softirq contexts where we need to *fake* holding the pin_mutex
are causing more trouble.

Still it would be nice if we did have a way to reassure ourselves that
the direct update to the context image is serialised with GPU execution.
In the meantime, stop lockdep complaining about false irq inversions.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111923
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191022122845.25038-1-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/gt/intel_gt_pm.c
drivers/gpu/drm/i915/gt/intel_lrc.c
drivers/gpu/drm/i915/gt/selftest_lrc.c
drivers/gpu/drm/i915/i915_perf.c