From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: anshuman.gupta@intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2] drm/xe/guc_pc: Reorder forcewake and xe_pm_runtime calls
Date: Thu, 20 Apr 2023 09:03:16 -0400 [thread overview]
Message-ID: <ZEE4FM3uzUZKnzp7@intel.com> (raw)
In-Reply-To: <20230420055648.323567-1-riana.tauro@intel.com>
On Thu, Apr 20, 2023 at 11:26:48AM +0530, Riana Tauro wrote:
> When the device is runtime suspended, reading some of the sysfs
> entries under device/gt#/ causes a resume error
> This is due to the ordering of pm_runtime and forcewake calls.
> Reorder to wake up using xe_pm_runtime_get and then forcewake
>
> v2: add goto statements (Rodrigo)
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Although I got myself wondering if we shouldn't add the mem_access
calls inside the forcewake or even the mmio functions...
>
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_pc.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c b/drivers/gpu/drm/xe/xe_guc_pc.c
> index 5a8d827ba770..b853831b342b 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
> @@ -370,15 +370,14 @@ static ssize_t freq_act_show(struct device *dev,
> u32 freq;
> ssize_t ret;
>
> + xe_device_mem_access_get(gt_to_xe(gt));
> /*
> * When in RC6, actual frequency is 0. Let's block RC6 so we are able
> * to verify that our freq requests are really happening.
> */
> ret = xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL);
> if (ret)
> - return ret;
> -
> - xe_device_mem_access_get(gt_to_xe(gt));
> + goto out;
>
> if (xe->info.platform == XE_METEORLAKE) {
> freq = xe_mmio_read32(gt, MTL_MIRROR_TARGET_WP1.reg);
> @@ -388,11 +387,11 @@ static ssize_t freq_act_show(struct device *dev,
> freq = REG_FIELD_GET(GEN12_CAGF_MASK, freq);
> }
>
> - xe_device_mem_access_put(gt_to_xe(gt));
> -
> ret = sysfs_emit(buf, "%d\n", decode_freq(freq));
>
> XE_WARN_ON(xe_force_wake_put(gt_to_fw(gt), XE_FORCEWAKE_ALL));
> +out:
> + xe_device_mem_access_put(gt_to_xe(gt));
> return ret;
> }
> static DEVICE_ATTR_RO(freq_act);
> @@ -405,22 +404,23 @@ static ssize_t freq_cur_show(struct device *dev,
> u32 freq;
> ssize_t ret;
>
> + xe_device_mem_access_get(gt_to_xe(gt));
> /*
> * GuC SLPC plays with cur freq request when GuCRC is enabled
> * Block RC6 for a more reliable read.
> */
> ret = xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL);
> if (ret)
> - return ret;
> + goto out;
>
> - xe_device_mem_access_get(gt_to_xe(gt));
> freq = xe_mmio_read32(gt, GEN6_RPNSWREQ.reg);
> - xe_device_mem_access_put(gt_to_xe(gt));
>
> freq = REG_FIELD_GET(REQ_RATIO_MASK, freq);
> ret = sysfs_emit(buf, "%d\n", decode_freq(freq));
>
> XE_WARN_ON(xe_force_wake_put(gt_to_fw(gt), XE_FORCEWAKE_ALL));
> +out:
> + xe_device_mem_access_put(gt_to_xe(gt));
> return ret;
> }
> static DEVICE_ATTR_RO(freq_cur);
> @@ -610,17 +610,17 @@ static ssize_t rc6_residency_show(struct device *dev,
> u32 reg;
> ssize_t ret;
>
> + xe_device_mem_access_get(pc_to_xe(pc));
> ret = xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL);
> if (ret)
> - return ret;
> + goto out;
>
> - xe_device_mem_access_get(pc_to_xe(pc));
> reg = xe_mmio_read32(gt, GEN6_GT_GFX_RC6.reg);
> - xe_device_mem_access_put(pc_to_xe(pc));
> -
> ret = sysfs_emit(buff, "%u\n", reg);
>
> XE_WARN_ON(xe_force_wake_put(gt_to_fw(gt), XE_FORCEWAKE_ALL));
> +out:
> + xe_device_mem_access_put(pc_to_xe(pc));
> return ret;
> }
> static DEVICE_ATTR_RO(rc6_residency);
> --
> 2.40.0
>
prev parent reply other threads:[~2023-04-20 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 5:56 [Intel-xe] [PATCH v2] drm/xe/guc_pc: Reorder forcewake and xe_pm_runtime calls Riana Tauro
2023-04-20 5:58 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/guc_pc: Reorder forcewake and xe_pm_runtime calls (rev2) Patchwork
2023-04-20 5:59 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-04-20 6:03 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-04-20 6:24 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-04-20 13:03 ` Rodrigo Vivi [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=ZEE4FM3uzUZKnzp7@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=riana.tauro@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