RE: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-22 Thread Quan, Evan
xander ; > pmen...@molgen.mpg.de; arthur.ma...@internode.on.net > Subject: Re: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI > > > > On 4/22/2022 2:23 PM, Quan, Evan wrote: > > [AMD Official Use Only] > > > > > > > >> -Original Message--

Re: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-22 Thread Lazar, Lijo
: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI On 4/22/2022 1:57 PM, Quan, Evan wrote: [AMD Official Use Only] -Original Message- From: Lazar, Lijo Sent: Monday, April 11, 2022 6:06 PM To: Quan, Evan ; amd-gfx@lists.freedesktop.org Cc: Deucher, Alexander ; pmen

RE: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-22 Thread Quan, Evan
6 PM > >> To: Quan, Evan ; amd-gfx@lists.freedesktop.org > >> Cc: Deucher, Alexander ; > >> pmen...@molgen.mpg.de; arthur.ma...@internode.on.net > >> Subject: Re: [PATCH V2] drm/amd/pm: fix the deadlock issue observed > >> on SI > >> > >>

Re: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-22 Thread Lazar, Lijo
: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI On 4/11/2022 2:24 PM, Evan Quan wrote: The adev->pm.mutx is already held at the beginning of amdgpu_dpm_compute_clocks/amdgpu_dpm_enable_uvd/amdgpu_dpm_ enable_vce. But on their calling path, amdgpu_display_bandwidth_upd

RE: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-22 Thread Quan, Evan
[AMD Official Use Only] > -Original Message- > From: Lazar, Lijo > Sent: Monday, April 11, 2022 6:06 PM > To: Quan, Evan ; amd-gfx@lists.freedesktop.org > Cc: Deucher, Alexander ; > pmen...@molgen.mpg.de; arthur.ma...@internode.on.net > Subject: Re: [PATC

RE: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-22 Thread Quan, Evan
[AMD Official Use Only] > -Original Message- > From: Thorsten Leemhuis > Sent: Thursday, April 21, 2022 4:29 PM > To: Quan, Evan ; amd-gfx@lists.freedesktop.org > Cc: Deucher, Alexander ; > pmen...@molgen.mpg.de; arthur.ma...@internode.on.net > Subject: Re: [PATC

Re: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-21 Thread Thorsten Leemhuis
On 11.04.22 10:54, Evan Quan wrote: > The adev->pm.mutx is already held at the beginning of > amdgpu_dpm_compute_clocks/amdgpu_dpm_enable_uvd/amdgpu_dpm_enable_vce. > But on their calling path, amdgpu_display_bandwidth_update will be > called and thus its sub functions amdgpu_dpm_get_sclk/mclk.

Re: [PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-11 Thread Lazar, Lijo
On 4/11/2022 2:24 PM, Evan Quan wrote: The adev->pm.mutx is already held at the beginning of amdgpu_dpm_compute_clocks/amdgpu_dpm_enable_uvd/amdgpu_dpm_enable_vce. But on their calling path, amdgpu_display_bandwidth_update will be called and thus its sub functions amdgpu_dpm_get_sclk/mclk.

[PATCH V2] drm/amd/pm: fix the deadlock issue observed on SI

2022-04-11 Thread Evan Quan
The adev->pm.mutx is already held at the beginning of amdgpu_dpm_compute_clocks/amdgpu_dpm_enable_uvd/amdgpu_dpm_enable_vce. But on their calling path, amdgpu_display_bandwidth_update will be called and thus its sub functions amdgpu_dpm_get_sclk/mclk. They will then try to acquire the same