Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH v9 14/26] drm/xe/xe_drm_client: Update handling of xe_force_wake_get return
Date: Tue, 15 Oct 2024 23:30:30 +0530	[thread overview]
Message-ID: <9bc7e679-b12b-4201-8e58-4e0746bc6dd9@intel.com> (raw)
In-Reply-To: <20241014075601.2324382-15-himal.prasad.ghimiray@intel.com>



On 14-10-2024 13:25, Himal Prasad Ghimiray wrote:
> xe_force_wake_get() now returns the reference count-incremented domain
> mask. If it fails for individual domains, the return value will always
> be 0. However, for XE_FORCEWAKE_ALL, it may return a non-zero value even
> in the event of failure. Use helper xe_force_wake_ref_has_domain to
> verify all domains are initialized or not. Update the return handling of
> xe_force_wake_get() to reflect this behavior, and ensure that the return
> value is passed as input to xe_force_wake_put().
> 
> v3
> - return xe_wakeref_t instead of int in xe_force_wake_get()
> - xe_force_wake_put() error doesn't need to be checked. It internally
> WARNS on domain ack failure.
> 
> v5
> - return unsigned int from xe_force_wake_get()
> 
> v6
> - use xe_force_wake_ref_has_domain()
> 
> v7
> - Fix commit message
> 
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_drm_client.c | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_drm_client.c b/drivers/gpu/drm/xe/xe_drm_client.c
> index fb52a23e28f8..22f0f1a6dfd5 100644
> --- a/drivers/gpu/drm/xe/xe_drm_client.c
> +++ b/drivers/gpu/drm/xe/xe_drm_client.c
> @@ -278,6 +278,7 @@ static void show_run_ticks(struct drm_printer *p, struct drm_file *file)
>   	struct xe_hw_engine *hwe;
>   	struct xe_exec_queue *q;
>   	u64 gpu_timestamp;
> +	unsigned int fw_ref;
>   
>   	xe_pm_runtime_get(xe);
>   
> @@ -303,13 +304,16 @@ static void show_run_ticks(struct drm_printer *p, struct drm_file *file)
>   			continue;
>   
>   		fw = xe_hw_engine_to_fw_domain(hwe);
> -		if (xe_force_wake_get(gt_to_fw(gt), fw)) {
> +
> +		fw_ref = xe_force_wake_get(gt_to_fw(gt), fw);
> +		if (!xe_force_wake_ref_has_domain(fw_ref, fw)) {
>   			hwe = NULL;
> +			xe_force_wake_put(gt_to_fw(gt), fw_ref);
>   			break;
>   		}
>   
>   		gpu_timestamp = xe_hw_engine_read_timestamp(hwe);
> -		XE_WARN_ON(xe_force_wake_put(gt_to_fw(gt), fw));
> +		xe_force_wake_put(gt_to_fw(gt), fw_ref);
>   		break;
>   	}

LGTM.
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>

Regards,
Badal

>   


  parent reply	other threads:[~2024-10-15 18:00 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  7:55 [PATCH v9 00/26] Fix xe_force_wake_get() failure handling Himal Prasad Ghimiray
2024-10-14  7:44 ` ✓ CI.Patch_applied: success for Fix xe_force_wake_get() failure handling (rev10) Patchwork
2024-10-14  7:44 ` ✓ CI.checkpatch: " Patchwork
2024-10-14  7:46 ` ✓ CI.KUnit: " Patchwork
2024-10-14  7:55 ` [PATCH v9 01/26] drm/xe: Add member initialized_domains to xe_force_wake() Himal Prasad Ghimiray
2024-10-14  7:55 ` [PATCH v9 02/26] drm/xe/forcewake: Change awake_domain datatype Himal Prasad Ghimiray
2024-10-14  7:55 ` [PATCH v9 03/26] drm/xe/forcewake: Add a helper xe_force_wake_ref_has_domain() Himal Prasad Ghimiray
2024-10-14  7:55 ` [PATCH v9 04/26] drm/xe: Error handling in xe_force_wake_get() Himal Prasad Ghimiray
2024-10-14  8:32   ` Nirmoy Das
2024-10-14  7:55 ` [PATCH v9 05/26] drm/xe: Modify xe_force_wake_put to handle _get returned mask Himal Prasad Ghimiray
2024-10-14  8:52   ` Nirmoy Das
2024-10-14  7:55 ` [PATCH v9 06/26] drm/xe/device: Update handling of xe_force_wake_get return Himal Prasad Ghimiray
2024-10-15 13:28   ` Nirmoy Das
2024-10-15 14:35   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 07/26] drm/xe/hdcp: " Himal Prasad Ghimiray
2024-10-15 13:29   ` Nirmoy Das
2024-10-14  7:55 ` [PATCH v9 08/26] drm/xe/gsc: " Himal Prasad Ghimiray
2024-10-15 13:57   ` Nirmoy Das
2024-10-14  7:55 ` [PATCH v9 09/26] drm/xe/gt: " Himal Prasad Ghimiray
2024-10-15 14:24   ` Nirmoy Das
2024-10-15 14:44   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 10/26] drm/xe/xe_gt_idle: " Himal Prasad Ghimiray
2024-10-15 14:25   ` Nirmoy Das
2024-10-14  7:55 ` [PATCH v9 11/26] drm/xe/devcoredump: " Himal Prasad Ghimiray
2024-10-15 14:26   ` Nirmoy Das
2024-10-15 16:06   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 12/26] drm/xe/tests/mocs: Update xe_force_wake_get() return handling Himal Prasad Ghimiray
2024-10-15 14:47   ` Nirmoy Das
2024-10-15 16:08   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 13/26] drm/xe/mocs: Update handling of xe_force_wake_get return Himal Prasad Ghimiray
2024-10-15 15:09   ` Nirmoy Das
2024-10-15 17:59   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 14/26] drm/xe/xe_drm_client: " Himal Prasad Ghimiray
2024-10-15 15:17   ` Nirmoy Das
2024-10-15 18:00   ` Nilawar, Badal [this message]
2024-10-14  7:55 ` [PATCH v9 15/26] drm/xe/xe_gt_debugfs: " Himal Prasad Ghimiray
2024-10-15 15:18   ` Nirmoy Das
2024-10-15 18:09   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 16/26] drm/xe/guc: " Himal Prasad Ghimiray
2024-10-15 15:20   ` Nirmoy Das
2024-10-15 18:32   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 17/26] drm/xe/huc: " Himal Prasad Ghimiray
2024-10-15 15:21   ` Nirmoy Das
2024-10-15 18:20   ` Nilawar, Badal
2024-10-15 18:42   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 18/26] drm/xe/oa: Handle force_wake_get failure in xe_oa_stream_init() Himal Prasad Ghimiray
2024-10-15 15:21   ` Nirmoy Das
2024-10-16 12:34   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 19/26] drm/xe/pat: Update handling of xe_force_wake_get return Himal Prasad Ghimiray
2024-10-15 15:28   ` Nirmoy Das
2024-10-16 12:35   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 20/26] drm/xe/gt_tlb_invalidation_ggtt: " Himal Prasad Ghimiray
2024-10-15 15:29   ` Nirmoy Das
2024-10-16 12:36   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 21/26] drm/xe/xe_reg_sr: " Himal Prasad Ghimiray
2024-10-15 15:30   ` Nirmoy Das
2024-10-16 12:38   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 22/26] drm/xe/query: " Himal Prasad Ghimiray
2024-10-15 15:31   ` Nirmoy Das
2024-10-16 12:40   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 23/26] drm/xe/vram: " Himal Prasad Ghimiray
2024-10-15 15:34   ` Nirmoy Das
2024-10-16 12:41   ` Nilawar, Badal
2024-10-14  7:55 ` [PATCH v9 24/26] drm/xe: forcewake debugfs open fails on xe_forcewake_get failure Himal Prasad Ghimiray
2024-10-15 16:02   ` Nilawar, Badal
2024-10-14  7:56 ` [PATCH v9 25/26] drm/xe: Ensure __must_check for xe_force_wake_get() return Himal Prasad Ghimiray
2024-10-14  8:57   ` Nirmoy Das
2024-10-14  7:56 ` [PATCH v9 26/26] drm/xe: Change return type to void for xe_force_wake_put Himal Prasad Ghimiray
2024-10-14  9:00   ` Nirmoy Das
2024-10-14  7:57 ` ✓ CI.Build: success for Fix xe_force_wake_get() failure handling (rev10) Patchwork
2024-10-14  7:59 ` ✓ CI.Hooks: " Patchwork
2024-10-14  8:01 ` ✓ CI.checksparse: " Patchwork
2024-10-14  8:27 ` ✓ CI.BAT: " Patchwork
2024-10-14  9:25 ` ✗ CI.FULL: failure " Patchwork
2024-10-17  5:40 ` ✓ CI.Patch_applied: success for Fix xe_force_wake_get() failure handling (rev11) Patchwork
2024-10-17  5:40 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-17  5:42 ` ✓ CI.KUnit: success " Patchwork
2024-10-17  5:53 ` ✓ CI.Build: " Patchwork
2024-10-17  5:55 ` ✓ CI.Hooks: " Patchwork
2024-10-17  5:57 ` ✓ CI.checksparse: " Patchwork
2024-10-17  6:20 ` ✓ CI.BAT: " Patchwork
2024-10-17 15:42 ` ✗ CI.FULL: failure " 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=9bc7e679-b12b-4201-8e58-4e0746bc6dd9@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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