RE: [PATCH] drm/amdgpu: put SMU into proper state on runpm suspending for BOCO capable platform

2021-12-24 Thread Quan, Evan
[AMD Official Use Only] > -Original Message- > From: Lazar, Lijo > Sent: Friday, December 24, 2021 12:44 PM > To: Quan, Evan ; amd-gfx@lists.freedesktop.org > Cc: Deucher, Alexander ; Chen, Guchun > > Subject: Re: [PATCH] drm/amdgpu: put SMU into proper state on runpm > suspending for

Re: [RFC v2 8/8] drm/amd/virt: Drop concurrent GPU reset protection for SRIOV

2021-12-24 Thread JingWen Chen
I do agree with shaoyun, if the host find the gpu engine hangs first, and do the flr, guest side thread may not know this and still try to access HW(e.g. kfd is using a lot of amdgpu_in_reset and reset_sem to identify the reset status). And this may lead to very bad result. On 2021/12/24

RE: [RFC v2 8/8] drm/amd/virt: Drop concurrent GPU reset protection for SRIOV

2021-12-24 Thread Deng, Emily
These patches look good to me. JingWen will pull these patches and do some basic TDR test on sriov environment, and give feedback. Best wishes Emily Deng >-Original Message- >From: Liu, Monk >Sent: Thursday, December 23, 2021 6:14 PM >To: Koenig, Christian ; Grodzovsky, Andrey >;

RE: [PATCH] drm/amdgpu: no DC support for headless chips

2021-12-24 Thread Chen, Guchun
[Public] Hi Alex, Thanks for clarification. The patch is: Reviewed-by: Guchun Chen . My concern is that amdgpu_device_has_dc_support is called at multiple places. Before this patch, for ARCTURUS and ALDEBARAN, it goes to default case, and returns true by default, but hardcoded IP discovery