diff options
| author | Matthew Auld <[email protected]> | 2023-01-30 10:12:27 +0000 |
|---|---|---|
| committer | Christian König <[email protected]> | 2023-02-06 12:10:13 +0100 |
| commit | 24243212c5ed2a5f3c1d1d74fd1913d8c189dec7 (patch) | |
| tree | b1705b09416fddf16303895595cb507de5b7b3ab /tools/perf/scripts/python/syscall-counts.py | |
| parent | 58c7ee0676bace7a7aae8a3e21ec8d09eab1c895 (diff) | |
drm/ttm: clear the ttm_tt when bo->resource is NULL
In the next few patches, when initially creating a ttm BO, the
bo->resource is NULL, and the driver is then expected to handle the
initial dummy move. However, if this is created as a system resource
the first ttm_tt we create will always have the clear value set to
false. Previously the initial ttm_tt would be created in
ttm_bo_validate() with the clear parameter always set to true.
Signed-off-by: Matthew Auld <[email protected]>
Reviewed-by: Christian König <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Acked-by: Nirmoy Das <[email protected]>
Signed-off-by: Christian König <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions