diff options
| author | Andrzej Hajda <andrzej.hajda@intel.com> | 2024-06-05 09:29:48 +0200 |
|---|---|---|
| committer | Matthew Brost <matthew.brost@intel.com> | 2024-06-05 11:28:33 -0700 |
| commit | 3ad7d18c5dad75ed38098c7cc3bc9594b4701399 (patch) | |
| tree | 38112af06871b220ca909b8461b6a975f52b5d75 /drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | |
| parent | 3494f5f5f675d84385b0f6bfcca1e10c739bf9bb (diff) | |
| download | linux-3ad7d18c5dad75ed38098c7cc3bc9594b4701399.tar.gz linux-3ad7d18c5dad75ed38098c7cc3bc9594b4701399.tar.bz2 linux-3ad7d18c5dad75ed38098c7cc3bc9594b4701399.zip | |
drm/xe: flush engine buffers before signalling user fence on all engines
Tests show that user fence signalling requires kind of write barrier,
otherwise not all writes performed by the workload will be available
to userspace. It is already done for render and compute, we need it
also for the rest: video, gsc, copy.
Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240605-fix_user_fence_posted-v3-2-06e7932f784a@intel.com
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c')
0 files changed, 0 insertions, 0 deletions