<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
</head>
<body>
<p style="font-family:Arial;font-size:10pt;color:#0078D7;margin:15pt;" align="Left">
[AMD Official Use Only - Internal Distribution Only]<br>
</p>
<br>
<div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
yes, IB test and vram restore will alloc IBs.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
I hit this issue for quite a long time ago. We test benchmarks on ARM server which is running android.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Hunders of processes hit too many issues. Panic and memory corruption everywhere.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Now i have a littke time to fix this deadlock.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
if you want to repro it, set gpu timeout to 50ms，then run vulkan,ocl, amdgputest, etc together.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
I believe you will see more weird issues.<br>
<br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Liu, Monk <Monk.Liu@amd.com><br>
<b>Sent:</b> Thursday, March 26, 2020 1:31:04 PM<br>
<b>To:</b> Pan, Xinhui <Xinhui.Pan@amd.com>; amd-gfx@lists.freedesktop.org <amd-gfx@lists.freedesktop.org><br>
<b>Cc:</b> Deucher, Alexander <Alexander.Deucher@amd.com>; Kuehling, Felix <Felix.Kuehling@amd.com>; Pan, Xinhui <Xinhui.Pan@amd.com>; Koenig, Christian <Christian.Koenig@amd.com><br>
<b>Subject:</b> RE: [RFC PATCH 0/2] add direct IB pool</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">That sounds a roughly doable plan to me , although we didn't hit this issue in our virtualization stress test but like a possible issue.<br>
<br>
>>> So the ring test above got stuck if no ib to alloc.<br>
Why there is IB alloc happened in ring test ? I remember there is no IB allocated for ring test, are you referring to IB test ?<br>
<br>
<br>
<br>
_____________________________________<br>
Monk Liu|GPU Virtualization Team |AMD<br>
<br>
<br>
-----Original Message-----<br>
From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> On Behalf Of xinhui pan<br>
Sent: Thursday, March 26, 2020 10:02 AM<br>
To: amd-gfx@lists.freedesktop.org<br>
Cc: Deucher, Alexander <Alexander.Deucher@amd.com>; Kuehling, Felix <Felix.Kuehling@amd.com>; Pan, Xinhui <Xinhui.Pan@amd.com>; Koenig, Christian <Christian.Koenig@amd.com><br>
Subject: [RFC PATCH 0/2] add direct IB pool<br>
<br>
druing gpu recovery, we alloc ibs for ring tests to test if recovery succeed or not.<br>
<br>
As gpu recovery parked the gpu scheduler thread, any pending jobs hold the ib resource has no chance to free. So the ring test above got stuck if no ib to alloc.<br>
<br>
If we schedule IBs directly in job_submit_direct, we can alloc ibs in the new ib pool. It should have less contention.<br>
<br>
If the IB could be freed in time, IOW, not depending on any scheduler, nor any other blocking code. It is better to alloc ibs in direct pool.<br>
<br>
xinhui pan (2):<br>
drm/amdgpu: add direct ib pool<br>
drm/amdgpu: use new job alloc variation if possible<br>
<br>
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +-<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c | 12 ++++++++++--<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 8 +++++++-<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_job.h | 3 ++-<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_jpeg.c | 2 +-<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 2 +-<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c | 2 +-<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c | 4 ++--<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 6 +++---<br>
drivers/gpu/drm/amd/amdgpu/amdgpu_vm_sdma.c | 3 ++-<br>
drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c | 4 ++--<br>
drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c | 4 ++--<br>
13 files changed, 35 insertions(+), 18 deletions(-)<br>
<br>
--<br>
2.17.1<br>
<br>
_______________________________________________<br>
amd-gfx mailing list<br>
amd-gfx@lists.freedesktop.org<br>
<a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7Cmonk.liu%40amd.com%7C1f5b1a3ba10a452c9de608d7d129b396%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637207850237679644&sdata=cS7S7a8gDmIgyJNbr4qXSPMZTLwKz0W429Z%2F2Zo6gek%3D&reserved=0">https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7Cmonk.liu%40amd.com%7C1f5b1a3ba10a452c9de608d7d129b396%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637207850237679644&sdata=cS7S7a8gDmIgyJNbr4qXSPMZTLwKz0W429Z%2F2Zo6gek%3D&reserved=0</a><br>
</div>
</span></font></div>
</div>
</body>
</html>