drm/amdgpu: unmap all user mappings of framebuffer and doorbell before mode1 reset

Browse source

During Mode 1 reset, the ASIC undergoes a reset cycle and becomes temporarily
inaccessible via PCIe. Any attempt to access framebuffer or MMIO registers during
this window can result in uncompleted PCIe transactions, leading to NMI panics or
system hangs.

To prevent this, Unmap all of the applications mappings of the framebuffer
and doorbell BARs before mode1 reset. Also prevent new mappings from coming in
during the reset process.

v2: remove inode in kfd_dev (Christian)
v3: correct unmap offset (Felix), remove prevent new mappings part
to avoid deadlock (Christian)

Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
Signed-off-by: Yifan Zhang <yifan1.zhang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Yifan Zhang 2026-05-11 22:14:23 +08:00 • committed by Alex Deucher

parent 633d6d808d

commit 70cadefcc6

5 changed files with 55 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

25

drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c

View file

1

drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h

View file

6

drivers/gpu/drm/amd/amdgpu/amdgpu_device.c

View file

22

drivers/gpu/drm/amd/amdkfd/kfd_chardev.c

View file

1

drivers/gpu/drm/amd/amdkfd/kfd_priv.h

View file