diff options
| author | Prike Liang <Prike.Liang@amd.com> | 2026-10-14 15:03:30 +0800 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2026-11-04 12:17:22 -0500 |
| commit | f5a0b3130f43c82a12399110044ab3afbc36fcdd (patch) | |
| tree | 259be068d16246d2ddbbc5f84da5051953a26b58 /include/linux/timerqueue.h | |
| parent | dcae66f5b9fe539e897aacca8e28bfe802478095 (diff) | |
drm/amdgpu/uvd: don't allocate or lock BOs in the direct IB test
The IB tests run inside GPU recovery, which must not allocate memory with
reclaim, take BO reservation locks or depend on eviction. The direct IB
pool and the job allocation use GFP_ATOMIC for this reason.
amdgpu_uvd_send_msg() still passes the UVD scheduler entity for direct
submissions, so drm_sched_job_init() allocates a scheduler fence with
GFP_KERNEL that the direct submission never uses. It also reserves the
message BO and adds the fence to it, which takes the reservation lock,
can allocate a fence slot with GFP_KERNEL and falls back to a blocking
dma_fence_wait().
Only pass the entity for scheduled submissions. The direct message BO is
only used by the IB test, which waits for each fence itself, so only fence
the BO for scheduled submissions.
Signed-off-by: Prike Liang <Prike.Liang@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit 1473ee6ae24d5b61c3165c444167a9d2069e1ab9)
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions
