Dear Jack,
Thank you for your patch.
Please add a colon after amdgpu/sriov in the commit message summary.
Am 07.01.21 um 11:46 schrieb Jack Zhang:
[Why]
When host trigger a whole gpu reset, guest will keep
*hosts trigger* or *host triggers*
waiting till host finish reset. But there's a
AM
To: Zhang, Hawking ; amd-gfx@lists.freedesktop.org; Liu,
Monk ; Chen, JingWen ; Deucher,
Alexander ; Deng, Emily
Subject: RE: [PATCH] amdgpu/sriov Stop data exchange for wholegpu reset
[AMD Official Use Only - Internal Distribution Only]
Ping...
-Original Message-
From: Zhang, Jack
exchange for wholegpu reset
Ping
-Original Message-
From: Jack Zhang
Sent: Thursday, January 7, 2021 6:47 PM
To: amd-gfx@lists.freedesktop.org
Cc: Zhang, Jack (Jian) ; Zhang, Jack (Jian)
; Chen, JingWen
Subject: [PATCH] amdgpu/sriov Stop data exchange for wholegpu reset
[Why]
When host
Ping
-Original Message-
From: Jack Zhang
Sent: Thursday, January 7, 2021 6:47 PM
To: amd-gfx@lists.freedesktop.org
Cc: Zhang, Jack (Jian) ; Zhang, Jack (Jian)
; Chen, JingWen
Subject: [PATCH] amdgpu/sriov Stop data exchange for wholegpu reset
[Why]
When host trigger a whole gpu reset
[Why]
When host trigger a whole gpu reset, guest will keep
waiting till host finish reset. But there's a work
queue in guest exchanging data between vf which need
to access frame buffer. During whole gpu reset, frame
buffer is not accessable, and this causes the call trace.
[How]
After vf get
