diff options
| author | Zhu Lingshan <lingshan.zhu@amd.com> | 2026-06-12 14:02:49 +0800 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2026-06-17 16:20:37 -0400 |
| commit | 97bcaf15ad25b14bd272fdff3616f9af5a8820c5 (patch) | |
| tree | a4b8b6cdb668c372c6e2f4a0e855986eb397b2d3 /drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | |
| parent | 9d748a8ac1ece966a712a3b3d81a39b6ec1cdd5c (diff) | |
| download | linux-next-97bcaf15ad25b14bd272fdff3616f9af5a8820c5.tar.gz linux-next-97bcaf15ad25b14bd272fdff3616f9af5a8820c5.zip | |
drm/amdgpu: implement per-process MES context
MES process context is a process-level page
where process specific context is saved for
MES scheduler.
However, current user-queue code path assigns
fw_obj of a queue to MES process_context_addr
when adding the queue to MES.
This means every new queue from the same process
would replace the previous process context address
with that queue's fw_obj address.
What's worse is, when user space frees a queue,
its fw_obj will be freed as well, causing MES
working on a NULL page pointer.
This issue leads to inconsistency and crash
in the scheduler.
This commit allocates a process-level page for
MES process contexts for a process other than queue-level
Signed-off-by: Zhu Lingshan <lingshan.zhu@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c')
0 files changed, 0 insertions, 0 deletions
