From: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdgpu: Fix crash when hot unplug in BACO.
Date: Fri, 21 May 2021 16:37:09 -0400 [thread overview]
Message-ID: <3ef2da30-fa95-ac63-4161-54fb23691045@amd.com> (raw)
In-Reply-To: <CADnq5_OVAVet7b614cDc0rS5fzwarjFtyP3nc9Ute3k5Hnbz1g@mail.gmail.com>
Will do.
Andrey
On 2021-05-21 4:18 p.m., Alex Deucher wrote:
> On Fri, May 21, 2021 at 4:14 PM Andrey Grodzovsky
> <andrey.grodzovsky@amd.com> wrote:
>> Problem:
>> When device goes into sleep state due to prolonged
>> innactivity (e.g. BACO sleep) and then hot unplugged,
>> PCI core will try to wake up the device as part of
>> unplug process. Since the device is gone all HW
>> programming during rpm resume fails leading
>> to a bad SW state later during pci remove handling.
>>
>> Fix:
>> Use a flag we use for PCIe error recovery to avoid
>> accessing registres. This allows to succefully complete
>> rpm resume sequence and finish pci remove.
> Might make sense to create a preliminary patch to change the name of
> this flag to something like no_hw_access since it's not specific to
> pci error handling.
>
> Alex
>
>> P.S Must use pci_device_is_present and not drm_dev_enter/exit
>> here since rpm resume happens before PCI remove and so the
>> unplug flag is not set yet.
>>
>> Link: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1081&data=04%7C01%7Candrey.grodzovsky%40amd.com%7C2a0ec02245b64de0139808d91c959987%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637572251118922092%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=egcYBxBU%2BkIqbEdypVueXQcWb%2Bqe%2BKCC30Mw%2FjgR6ag%3D&reserved=0
>> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
>> index d8db5929cdd9..ab95ebf56636 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
>> @@ -1555,6 +1555,11 @@ static int amdgpu_pmops_runtime_resume(struct device *dev)
>> if (!adev->runpm)
>> return -EINVAL;
>>
>> + /* Avoids registers access if device is physically gone */
>> + if (!pci_device_is_present(adev->pdev))
>> + adev->in_pci_err_recovery = true;
>> +
>> +
>> if (amdgpu_device_supports_px(drm_dev)) {
>> drm_dev->switch_power_state = DRM_SWITCH_POWER_CHANGING;
>>
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2021-05-21 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 20:14 [PATCH] drm/amdgpu: Fix crash when hot unplug in BACO Andrey Grodzovsky
2021-05-21 20:18 ` Alex Deucher
2021-05-21 20:37 ` Andrey Grodzovsky [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=3ef2da30-fa95-ac63-4161-54fb23691045@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@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