drm/i915/pool: constrain pool objects by mapping type

Browse source

In a few places we always end up mapping the pool object with the FORCE
constraint(to prevent hitting -EBUSY) which will destroy the cached
mapping if it has a different type. As a simple first step, make the
mapping type part of the pool interface, where the behaviour is to only
give out pool objects which match the requested mapping type.

Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: https://patchwork.freedesktop.org/patch/msgid/20210119133106.66294-4-matthew.auld@intel.com

...

This commit is contained in:

Matthew Auld 2021-01-19 13:31:06 +00:00 • committed by Chris Wilson

parent e2f4367a47

commit 8f47c8c3b0

6 changed files with 25 additions and 17 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

13

drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c

View file

8

drivers/gpu/drm/i915/gem/i915_gem_object_blt.c

View file

12

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

View file

3

drivers/gpu/drm/i915/gt/intel_gt_buffer_pool.h

View file

4

drivers/gpu/drm/i915/gt/intel_gt_buffer_pool_types.h

View file

2

drivers/gpu/drm/i915/i915_cmd_parser.c

View file