diff options
| author | Matthew Auld <matthew.auld@intel.com> | 2022-03-24 17:21:42 +0000 |
|---|---|---|
| committer | Matthew Auld <matthew.auld@intel.com> | 2022-03-29 09:10:43 +0100 |
| commit | 66ddc69373a8d5a08fe4341d9e912bfdac602248 (patch) | |
| tree | e62d086d24434e13567f97eef1ec46213fc90e81 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | d8b932014c4aa5a70bb6add0f14d9329e7c489c2 (diff) | |
drm/i915/ttm: limit where we apply TTM_PL_FLAG_CONTIGUOUS
We only need this when allocating device local-memory, where this
influences the drm_buddy. Currently there is some funny behaviour where
an "in limbo" system memory object is lacking the relevant placement
flags etc. before we first allocate the ttm_tt, leading to ttm
performing a move when not needed, since the current placement is seen
as not compatible.
Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Fixes: 2ed38cec5606 ("drm/i915: opportunistically apply ALLOC_CONTIGIOUS")
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Acked-by: Nirmoy Das <nirmoy.das@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220324172143.377104-1-matthew.auld@intel.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions