diff options
| author | Thomas Hellström <[email protected]> | 2021-08-13 16:43:31 +0200 |
|---|---|---|
| committer | Thomas Hellström <[email protected]> | 2021-08-25 16:05:47 +0200 |
| commit | 669076334bfa7915e6856cf49c6408a2ec07df7a (patch) | |
| tree | 63606a28faf8349b92064efee6c867f5c46b45db /tools/perf/scripts/python/bin | |
| parent | d8ac30fd479cf0f0b37c7f06b06b50c18f57c548 (diff) | |
drm/ttm, drm/i915: Update ttm_move_memcpy for async use
The buffer object argument to ttm_move_memcpy was only used to
determine whether the destination memory should be cleared only
or whether we should copy data. Replace it with a "clear" bool, and
update the callers.
The intention here is to be able to use ttm_move_memcpy() async under
a dma-fence as a fallback if an accelerated blit fails in a security-
critical path where data might leak if the blit is not properly
performed. For that purpose the bo is an unsuitable argument since
its relevant members might already have changed at call time.
Finally, update the ttm_move_memcpy kerneldoc that seems to have
ended up with a stale version.
Cc: Christian König <[email protected]>
Signed-off-by: Thomas Hellström <[email protected]>
Reviewed-by: Matthew Auld <[email protected]>
Reviewed-by: Christian König <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions