drm/i915: Track ggtt fence reservations under its own mutex

Browse source

We can reduce the locking for fence registers from the dev->struct_mutex
to a local mutex. We could introduce a mutex for the sole purpose of
tracking the fence acquisition, except there is a little bit of overlap
with the fault tracking, so use the i915_ggtt.mutex as it covers both.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190822060914.2671-1-chris@chris-wilson.co.uk

...

This commit is contained in:

Chris Wilson 2019-08-22 07:09:12 +01:00

parent 8e458fe2ee

commit e2ccc50a3a

6 changed files with 87 additions and 49 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

7

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

View file

10

drivers/gpu/drm/i915/gvt/aperture_gm.c

View file

5

drivers/gpu/drm/i915/i915_debugfs.c

View file

108

drivers/gpu/drm/i915/i915_gem_fence_reg.c

View file

2

drivers/gpu/drm/i915/i915_gem_fence_reg.h

View file

4

drivers/gpu/drm/i915/i915_vma.h

View file