diff options
| author | Alex Deucher <alexander.deucher@amd.com> | 2026-03-16 11:04:46 -0400 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2026-03-17 18:03:09 -0400 |
| commit | e9f58ff991dd4be13fd7a651bbf64329c090af09 (patch) | |
| tree | ccb54786f65431ed23fc1c022c8fa9f388378873 /include/linux/syscall_user_dispatch.h | |
| parent | 3fc4648b53b7e393b91e63600e28e6f25c8ef0c5 (diff) | |
drm/amdgpu: rework how we handle TLB fences
Add a new VM flag to indicate whether or not we need
a TLB fence. Userqs (KFD or KGD) require a TLB fence.
A TLB fence is not strictly required for kernel queues,
but it shouldn't hurt. That said, enabling this
unconditionally should be fine, but it seems to tickle
some issues in KIQ/MES. Only enable them for KFD,
or when KGD userq queues are enabled (currently via module
parameter).
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4798
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4749
Fixes: f3854e04b708 ("drm/amdgpu: attach tlb fence to the PTs update")
Cc: Christian König <christian.koenig@amd.com>
Cc: Prike Liang <Prike.Liang@amd.com>
Reviewed-by: Prike Liang <Prike.Liang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit 69c5fbd2b93b5ced77c6e79afe83371bca84c788)
Cc: stable@vger.kernel.org
Diffstat (limited to 'include/linux/syscall_user_dispatch.h')
0 files changed, 0 insertions, 0 deletions