From: Felix Kuehling <felix.kuehling@amd.com>
To: Lijo Lazar <lijo.lazar@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Hawking.Zhang@amd.com, Alexander.Deucher@amd.com, Asad.Kamal@amd.com
Subject: Re: [PATCH] drm/amdgpu: Do a basic health check before reset
Date: Wed, 13 Mar 2024 15:49:15 -0400 [thread overview]
Message-ID: <aec029aa-8ceb-4450-9139-27c7dda43f98@amd.com> (raw)
In-Reply-To: <20240313094132.668370-1-lijo.lazar@amd.com>
On 2024-03-13 5:41, Lijo Lazar wrote:
> Check if the device is present in the bus before trying to recover. It
> could be that device itself is lost from the bus in some hang
> situations.
>
> Signed-off-by: Lijo Lazar <lijo.lazar@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 24 ++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index 1e9454e6e4cb..b37113b79483 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -5536,6 +5536,23 @@ static inline void amdgpu_device_stop_pending_resets(struct amdgpu_device *adev)
>
> }
>
> +static int amdgpu_device_health_check(struct list_head *device_list_handle)
> +{
> + struct amdgpu_device *tmp_adev;
> + int ret = 0;
> + u32 status;
> +
> + list_for_each_entry(tmp_adev, device_list_handle, reset_list) {
> + pci_read_config_dword(tmp_adev->pdev, PCI_COMMAND, &status);
> + if (PCI_POSSIBLE_ERROR(status)) {
> + dev_err(tmp_adev->dev, "device lost from bus!");
> + ret = -ENODEV;
You could just return here. What's the point of looking for other
devices if you're going to return an error anyway?
Regards,
Felix
> + }
> + }
> +
> + return ret;
> +}
> +
> /**
> * amdgpu_device_gpu_recover - reset the asic and recover scheduler
> *
> @@ -5607,6 +5624,12 @@ int amdgpu_device_gpu_recover(struct amdgpu_device *adev,
> device_list_handle = &device_list;
> }
>
> + if (!amdgpu_sriov_vf(adev)) {
> + r = amdgpu_device_health_check(device_list_handle);
> + if (r)
> + goto end_reset;
> + }
> +
> /* We need to lock reset domain only once both for XGMI and single device */
> tmp_adev = list_first_entry(device_list_handle, struct amdgpu_device,
> reset_list);
> @@ -5772,6 +5795,7 @@ int amdgpu_device_gpu_recover(struct amdgpu_device *adev,
> reset_list);
> amdgpu_device_unlock_reset_domain(tmp_adev->reset_domain);
>
> +end_reset:
> if (hive) {
> mutex_unlock(&hive->hive_lock);
> amdgpu_put_xgmi_hive(hive);
next prev parent reply other threads:[~2024-03-13 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 9:41 [PATCH] drm/amdgpu: Do a basic health check before reset Lijo Lazar
2024-03-13 9:48 ` Kamal, Asad
2024-03-13 19:49 ` Felix Kuehling [this message]
2024-03-14 4:41 ` Lazar, Lijo
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=aec029aa-8ceb-4450-9139-27c7dda43f98@amd.com \
--to=felix.kuehling@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Asad.Kamal@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=lijo.lazar@amd.com \
/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;
as well as URLs for NNTP newsgroup(s).