diff options
| author | Matthew Auld <matthew.auld@intel.com> | 2021-01-19 13:31:06 +0000 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2021-01-19 20:36:28 +0000 |
| commit | 8f47c8c3b06fdc0d024c29ae230bdd6522de91be (patch) | |
| tree | 8fa7d63f0a5b5edcc29fd2fb1e0ec7f7054b5769 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | e2f4367a475be1db09276112dd5306a932dba2d2 (diff) | |
drm/i915/pool: constrain pool objects by mapping type
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
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions