diff options
| author | Nirmoy Das <[email protected]> | 2024-04-30 18:25:29 +0200 |
|---|---|---|
| committer | Nirmoy Das <[email protected]> | 2024-05-06 18:14:11 +0200 |
| commit | a0862cf2febcc37188ab47441b69960c8c8f3fa3 (patch) | |
| tree | 0576251cb565fbc6e028321a6e84e6855d4ee209 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | a4b725767d93e3564019906ad43908b8bf3d4d9e (diff) | |
drm/xe: Refactor default device atomic settings
The default behavior of device atomics depends on the
VM type and buffer allocation types. Device atomics are
expected to function with all types of allocations for
traditional applications/APIs. Additionally, in compute/SVM
API scenarios with fault mode or LR mode VMs, device atomics
must work with single-region allocations. In all other cases
device atomics should be disabled by default also on platforms
where we know device atomics doesn't on work on particular
allocations types.
v3: fault mode requires LR mode so only check for LR mode
to determine compute API(Jose).
Handle SMEM+LMEM BO's migration to LMEM where device
atomics is expected to work. (Brian).
v2: Fix platform checks to correct atomics behaviour on PVC.
Acked-by: Michal Mrozek <[email protected]>
Reviewed-by: Oak Zeng <[email protected]>
Acked-by: Lionel Landwerlin <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Signed-off-by: Nirmoy Das <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions