Am 27.08.19 um 10:34 schrieb Monk Liu:
for SOC15/vega10 the BACO reset & mode1 would introduce vram lost
in high end address range, current kmd's vram lost checking cannot
catch it since it only check very ahead visible frame buffer
Looks mostly good to me.
Only question I have is why to use a
sure
_
Monk Liu|GPU Virtualization Team |AMD
[sig-cloud-gpu]
From: Deucher, Alexander
Sent: Tuesday, August 27, 2019 8:48 PM
To: Liu, Monk ; amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: introduce vram lost for reset
Can you update nv.c as
Can you update nv.c as well? With that fixed,
Reviewed-by: Alex Deucher
From: amd-gfx on behalf of Monk Liu
Sent: Tuesday, August 27, 2019 4:34 AM
To: amd-gfx@lists.freedesktop.org
Cc: Liu, Monk
Subject: [PATCH] drm/amdgpu: introduce vram lost for reset
for SOC15/vega10 the BACO reset & mode1 would introduce vram lost
in high end address range, current kmd's vram lost checking cannot
catch it since it only check very ahead visible frame buffer
Signed-off-by: Monk Liu
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h| 1 +
drivers/gpu/drm/amd/amdg
