From: Felix Kuehling <felix.kuehling@amd.com>
To: "Liu, Shaoyun" <Shaoyun.Liu@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amd/amdgpu: fix the kfd pre_reset sequence in sriov
Date: Fri, 5 Nov 2021 17:10:50 -0400 [thread overview]
Message-ID: <124e31fb-de4b-d307-8919-353f61bd6b4a@amd.com> (raw)
In-Reply-To: <DM6PR12MB55345EA86293817DE5B71C6EF48E9@DM6PR12MB5534.namprd12.prod.outlook.com>
On 2021-11-05 1:59 p.m., Liu, Shaoyun wrote:
> [AMD Official Use Only]
>
> Ye, a lot already been changed since then , now the pre_reset and post_reset not in the lock/unlock anymore. With my previous change , we make kfd_pre_reset avoid touch HW . Now it's pure SW handling , should be safe to be moved out of the full access .
> Anyway, thanks to bring this up, it will remind us to verify on the XGMI configuration on SRIOV.
OK. Assuming it doesn't break in your testing, consider the patch
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
>
> Regards
> shaoyun.liu
>
> -----Original Message-----
> From: Kuehling, Felix <Felix.Kuehling@amd.com>
> Sent: Friday, November 5, 2021 1:48 PM
> To: Liu, Shaoyun <Shaoyun.Liu@amd.com>; amd-gfx@lists.freedesktop.org
> Subject: Re: [PATCH] drm/amd/amdgpu: fix the kfd pre_reset sequence in sriov
>
> There was a reason why pre_reset was done differently on SRIOV. However, the code has changed a lot since then. Is this concern still valid?
>
>> commit 7b184b006185215daf4e911f8de212964c99a514
>> Author: wentalou <Wentao.Lou@amd.com>
>> Date: Fri Dec 7 13:53:18 2018 +0800
>>
>> drm/amdgpu: kfd_pre_reset outside req_full_gpu cause sriov hang
>>
>> XGMI hive put kfd_pre_reset into amdgpu_device_lock_adev,
>> but outside req_full_gpu of sriov.
>> It would make sriov hang during reset.
>>
>> Signed-off-by: Wentao Lou <Wentao.Lou@amd.com>
>> Reviewed-by: Shaoyun Liu <Shaoyun.Liu@amd.com>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> Regards,
> Felix
>
>
> On 2021-11-05 12:57 p.m., shaoyunl wrote:
>> The KFD pre_reset should be called before reset been executed, it will
>> hold the lock to prevent other rocm process to sent the packlage to
>> hiq during host execute the real reset on the HW
>>
>> Signed-off-by: shaoyunl <shaoyun.liu@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 5 +----
>> 1 file changed, 1 insertion(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> index 95fec36e385e..d7c9dce17cad 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> @@ -4278,8 +4278,6 @@ static int amdgpu_device_reset_sriov(struct amdgpu_device *adev,
>> if (r)
>> return r;
>>
>> - amdgpu_amdkfd_pre_reset(adev);
>> -
>> /* Resume IP prior to SMC */
>> r = amdgpu_device_ip_reinit_early_sriov(adev);
>> if (r)
>> @@ -5015,8 +5013,7 @@ int amdgpu_device_gpu_recover(struct
>> amdgpu_device *adev,
>>
>> cancel_delayed_work_sync(&tmp_adev->delayed_init_work);
>>
>> - if (!amdgpu_sriov_vf(tmp_adev))
>> - amdgpu_amdkfd_pre_reset(tmp_adev);
>> + amdgpu_amdkfd_pre_reset(tmp_adev);
>>
>> /*
>> * Mark these ASICs to be reseted as untracked first
prev parent reply other threads:[~2021-11-05 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 16:57 [PATCH] drm/amd/amdgpu: fix the kfd pre_reset sequence in sriov shaoyunl
2021-11-05 17:48 ` Felix Kuehling
2021-11-05 17:59 ` Liu, Shaoyun
2021-11-05 21:10 ` Felix Kuehling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=124e31fb-de4b-d307-8919-353f61bd6b4a@amd.com \
--to=felix.kuehling@amd.com \
--cc=Shaoyun.Liu@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox