From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: "Kim, Jonathan" <Jonathan.Kim@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Kasiviswanathan, Harish" <Harish.Kasiviswanathan@amd.com>
Subject: Re: [PATCH] drm/amdgpu: fix gpu recovery disable with per queue reset
Date: Fri, 10 Jan 2025 09:08:56 +0530 [thread overview]
Message-ID: <f7a71dc8-7643-431e-8c92-ade74619ef2c@amd.com> (raw)
In-Reply-To: <CY8PR12MB7435645F2AB787B7BC57BB0A85132@CY8PR12MB7435.namprd12.prod.outlook.com>
On 1/9/2025 8:27 PM, Kim, Jonathan wrote:
> [Public]
>
>> -----Original Message-----
>> From: Lazar, Lijo <Lijo.Lazar@amd.com>
>> Sent: Thursday, January 9, 2025 1:14 AM
>> To: Kim, Jonathan <Jonathan.Kim@amd.com>; amd-gfx@lists.freedesktop.org
>> Cc: Kasiviswanathan, Harish <Harish.Kasiviswanathan@amd.com>
>> Subject: Re: [PATCH] drm/amdgpu: fix gpu recovery disable with per queue reset
>>
>>
>>
>> On 1/9/2025 1:31 AM, Jonathan Kim wrote:
>>> Per queue reset should be bypassed when gpu recovery is disabled
>>> with module parameter.
>>>
>>> Signed-off-by: Jonathan Kim <jonathan.kim@amd.com>
>>> ---
>>> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c
>>> index cc66ebb7bae1..441568163e20 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c
>>> @@ -1131,6 +1131,9 @@ uint64_t kgd_gfx_v9_hqd_get_pq_addr(struct
>> amdgpu_device *adev,
>>> uint32_t low, high;
>>> uint64_t queue_addr = 0;
>>>
>>> + if (!amdgpu_gpu_recovery)
>>> + return 0;
>>> +
>>> kgd_gfx_v9_acquire_queue(adev, pipe_id, queue_id, inst);
>>> amdgpu_gfx_rlc_enter_safe_mode(adev, inst);
>>>
>>> @@ -1179,6 +1182,9 @@ uint64_t kgd_gfx_v9_hqd_reset(struct amdgpu_device
>> *adev,
>>> uint32_t low, high, pipe_reset_data = 0;
>>> uint64_t queue_addr = 0;
>>>
>>> + if (!amdgpu_gpu_recovery)
>>> + return 0;
>>> +
>>
>> I think the right place for this check is not inside callback, should be
>> from the place where the callback gets called.
>
> I don't think it really matters. We're going to have different reset types in the future that my come from different callers.
> It's probably easier to remember to put the bypass where the reset is actually happening.
>
If I want to define something like amdgpu_gpu_recovery=2 (don't do queue
reset but perform other resets), then it matters.
Since this is a callback, keeping it at the wrapper place may be more
maintainable rather than keeping the check for gfx10/11/12 etc.
Thanks,
Lijo
> Jon
>
>>
>> Thanks,
>> Lijo
>>
>>> kgd_gfx_v9_acquire_queue(adev, pipe_id, queue_id, inst);
>>> amdgpu_gfx_rlc_enter_safe_mode(adev, inst);
>>>
>
next prev parent reply other threads:[~2025-01-10 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 20:01 [PATCH] drm/amdgpu: fix gpu recovery disable with per queue reset Jonathan Kim
2025-01-08 20:32 ` Alex Deucher
2025-01-09 6:14 ` Lazar, Lijo
2025-01-09 14:57 ` Kim, Jonathan
2025-01-10 3:38 ` Lazar, Lijo [this message]
2025-01-10 16:13 ` Kim, Jonathan
2025-01-10 16:29 ` Lazar, Lijo
2025-01-10 21:23 ` Kim, Jonathan
2025-01-11 3:36 ` Lazar, Lijo
2025-01-14 17:21 ` Kim, Jonathan
2025-01-15 8:29 ` Lazar, Lijo
2025-01-15 8:32 ` 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=f7a71dc8-7643-431e-8c92-ade74619ef2c@amd.com \
--to=lijo.lazar@amd.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=Jonathan.Kim@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