drm/i915: Drop assertion that ce->pin_mutex guards state updates

Browse source

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

...

This commit is contained in:

Chris Wilson 2019-10-22 13:28:45 +01:00

parent e948761f5b

commit 0587152bf9

4 changed files with 0 additions and 24 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

drivers/gpu/drm/i915/gt/intel_gt_pm.c

View file

16

drivers/gpu/drm/i915/gt/intel_lrc.c

View file

5

drivers/gpu/drm/i915/gt/selftest_lrc.c

View file

1

drivers/gpu/drm/i915/i915_perf.c

View file