Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: imre.deak@intel.com, Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	"Francois Dugast" <francois.dugast@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH] drm/i915: Convert intel_runtime_pm_get_noresume towards raw wakeref
Date: Fri, 19 Apr 2024 12:06:48 +0300	[thread overview]
Message-ID: <87a5lpwwk7.fsf@intel.com> (raw)
In-Reply-To: <ZiGzwL7Rq6OzWCbb@ideak-desk.fi.intel.com>

On Fri, 19 Apr 2024, Imre Deak <imre.deak@intel.com> wrote:
> On Thu, Apr 18, 2024 at 06:37:56PM -0400, Rodrigo Vivi wrote:
>> In the past, the noresume function was used by the GEM code to ensure
>> wakelocks were held and bump its usage. This is no longer the case
>> and this function was totally unused until it started to be used again
>> by display with commit 77e619a82fc3 ("drm/i915/display: convert inner
>> wakeref get towards get_if_in_use")
>> 
>> However, on the display code, most of the callers are using the
>> raw wakeref, rather then the wakelock version. What caused a
>> major regression caught by CI.
>> 
>> Another option to this patch is to go with the original plan and
>> use the get_if_in_use variant in the display code, what is enough
>> to fulfil our needs. Then, an extra patch to delete the unused
>> _noresume variant.
>> 
>> v2: Keep grabbing wakelock but only assert for wakeref. (Imre)
>> 
>> Cc: Imre Deak <imre.deak@intel.com>
>> Cc: Francois Dugast <francois.dugast@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Fixes: 77e619a82fc3 ("drm/i915/display: convert inner wakeref get towards get_if_in_use")
>> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/10875
>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Reviewed-by: Imre Deak <imre.deak@intel.com>

Thanks for the patch and review. Pushed to drm-xe-next where the
offending commit was pushed.

BR,
Jani.


>
>> ---
>>  drivers/gpu/drm/i915/display/intel_display_power.c |  6 ------
>>  drivers/gpu/drm/i915/intel_runtime_pm.c            | 14 +++++---------
>>  2 files changed, 5 insertions(+), 15 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.c b/drivers/gpu/drm/i915/display/intel_display_power.c
>> index 048943d0a881..03dc7edcc443 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_power.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_power.c
>> @@ -640,12 +640,6 @@ release_async_put_domains(struct i915_power_domains *power_domains,
>>  	enum intel_display_power_domain domain;
>>  	intel_wakeref_t wakeref;
>>  
>> -	/*
>> -	 * The caller must hold already raw wakeref, upgrade that to a proper
>> -	 * wakeref to make the state checker happy about the HW access during
>> -	 * power well disabling.
>> -	 */
>> -	assert_rpm_raw_wakeref_held(rpm);
>>  	wakeref = intel_runtime_pm_get_noresume(rpm);
>>  
>>  	for_each_power_domain(domain, mask) {
>> diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c b/drivers/gpu/drm/i915/intel_runtime_pm.c
>> index d4e844128826..2d0647aca964 100644
>> --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
>> +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
>> @@ -272,15 +272,11 @@ intel_wakeref_t intel_runtime_pm_get_if_active(struct intel_runtime_pm *rpm)
>>   * intel_runtime_pm_get_noresume - grab a runtime pm reference
>>   * @rpm: the intel_runtime_pm structure
>>   *
>> - * This function grabs a device-level runtime pm reference (mostly used for GEM
>> - * code to ensure the GTT or GT is on).
>> + * This function grabs a device-level runtime pm reference.
>>   *
>> - * It will _not_ power up the device but instead only check that it's powered
>> - * on.  Therefore it is only valid to call this functions from contexts where
>> - * the device is known to be powered up and where trying to power it up would
>> - * result in hilarity and deadlocks. That pretty much means only the system
>> - * suspend/resume code where this is used to grab runtime pm references for
>> - * delayed setup down in work items.
>> + * It will _not_ resume the device but instead only get an extra wakeref.
>> + * Therefore it is only valid to call this functions from contexts where
>> + * the device is known to be active and with another wakeref previously hold.
>>   *
>>   * Any runtime pm reference obtained by this function must have a symmetric
>>   * call to intel_runtime_pm_put() to release the reference again.
>> @@ -289,7 +285,7 @@ intel_wakeref_t intel_runtime_pm_get_if_active(struct intel_runtime_pm *rpm)
>>   */
>>  intel_wakeref_t intel_runtime_pm_get_noresume(struct intel_runtime_pm *rpm)
>>  {
>> -	assert_rpm_wakelock_held(rpm);
>> +	assert_rpm_raw_wakeref_held(rpm);
>>  	pm_runtime_get_noresume(rpm->kdev);
>>  
>>  	intel_runtime_pm_acquire(rpm, true);
>> -- 
>> 2.44.0
>> 

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-04-19  9:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 22:13 [PATCH] drm/i915: Convert intel_runtime_pm_get_noresume towards raw wakeref Rodrigo Vivi
2024-04-18 22:30 ` Imre Deak
2024-04-18 22:34   ` Rodrigo Vivi
2024-04-18 22:37   ` Rodrigo Vivi
2024-04-18 23:58     ` Imre Deak
2024-04-19  9:06       ` Jani Nikula [this message]
2024-04-18 23:57 ` ✓ CI.Patch_applied: success for drm/i915: Convert intel_runtime_pm_get_noresume towards raw wakeref (rev2) Patchwork
2024-04-18 23:58 ` ✓ CI.checkpatch: " Patchwork
2024-04-18 23:58 ` ✓ CI.KUnit: " Patchwork
2024-04-19  0:10 ` ✓ CI.Build: " Patchwork
2024-04-19  0:14 ` ✓ CI.Hooks: " Patchwork
2024-04-19  0:15 ` ✗ CI.checksparse: warning " Patchwork
2024-04-19  1:24 ` ✓ CI.BAT: success " Patchwork
2024-04-20 19:07 ` ✓ CI.FULL: " Patchwork

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=87a5lpwwk7.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=francois.dugast@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=ville.syrjala@linux.intel.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