On 11.04.22 09:59, Paul Menzel wrote:
> Am 11.04.22 um 09:47 schrieb Evan Quan:
>
> As it’s a regression, please follow the documentation, and add the
> related tags.
Yes please, otherwise you break tools that reply on this, like my
regression tracking efforts.
> Fixes: 3712e7a49459 ("drm/amd/pm:
On 4/11/2022 2:55 PM, Quan, Evan wrote:
[AMD Official Use Only]
-Original Message-
From: Lazar, Lijo
Sent: Monday, April 11, 2022 5:05 PM
To: Quan, Evan ; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ;
arthur.ma...@internode.on.net
Subject: Re: [PATCH] drm/amd/pm: fix the
[AMD Official Use Only]
> -Original Message-
> From: Lazar, Lijo
> Sent: Monday, April 11, 2022 5:05 PM
> To: Quan, Evan ; amd-gfx@lists.freedesktop.org
> Cc: Deucher, Alexander ;
> arthur.ma...@internode.on.net
> Subject: Re: [PATCH] drm/amd/pm: fix the deadlock
On 4/11/2022 1:17 PM, Evan Quan wrote:
By placing those unrelated code outside of adev->pm.mutex
protections or restructuring the call flow, we can eliminate
the deadlock issue. This comes with no real logics change.
Fixes: 3712e7a49459 ("drm/amd/pm: unified lock protections in amdgpu_dpm.c")
si...@lists.linux.dev
> Subject: Re: [PATCH] drm/amd/pm: fix the deadlock issue observed on SI
>
> Dear Evan,
>
>
> It would have been nice, if you put me in Cc as I also reported the
> regression.
>
> Am 11.04.22 um 09:47 schrieb Evan Quan:
> > By placing thos
Dear Evan,
It would have been nice, if you put me in Cc as I also reported the
regression.
Am 11.04.22 um 09:47 schrieb Evan Quan:
By placing those unrelated code outside of adev->pm.mutex
protections or restructuring the call flow, we can eliminate
the deadlock issue. This comes with no rea
By placing those unrelated code outside of adev->pm.mutex
protections or restructuring the call flow, we can eliminate
the deadlock issue. This comes with no real logics change.
Fixes: 3712e7a49459 ("drm/amd/pm: unified lock protections in amdgpu_dpm.c")
Signed-off-by: Evan Quan
Change-Id: I75de
