From: "K V P, Satyanarayana" <satyanarayana.k.v.p@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/guc: Don't invoke disable_ct action during replacement
Date: Mon, 8 Sep 2025 16:27:49 +0530 [thread overview]
Message-ID: <2d7c2a72-2589-4e82-8aca-1c239711391e@intel.com> (raw)
In-Reply-To: <20250908102053.539-3-michal.wajdeczko@intel.com>
On 08-09-2025 15:50, Michal Wajdeczko wrote:
> During second CT initialization step, known as post_hwconfig, we
> want to replace previously registered CT disable devm action to
> make sure it will be invoked prior to releasing underlying BO.
>
> But to replace this action we don't need to execute it right away
> since we know that CT was disabled prior to that late init step
> and we already assert that. Use devm_remove_action() instead to
> avoid extra message about 'disabling CT' that could be seen now:
>
> [drm:guc_ct_change_state [xe]] GT0: GuC CT communication channel disabled
> ...
> DEVRES REM ff11000149320940 guc_action_disable_ct (16 bytes)
> [drm:guc_ct_change_state [xe]] GT0: GuC CT communication channel disabled
> DEVRES ADD ff110001664fc040 guc_action_disable_ct (16 bytes)
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_ct.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> index 12372d5b7067..bb8650fdeb45 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> @@ -306,7 +306,7 @@ int xe_guc_ct_init_post_hwconfig(struct xe_guc_ct *ct)
> return ret;
> }
>
> - devm_release_action(xe->drm.dev, guc_action_disable_ct, ct);
> + devm_remove_action(xe->drm.dev, guc_action_disable_ct, ct);
> return devm_add_action_or_reset(xe->drm.dev, guc_action_disable_ct, ct);
> }
>
LGTM.
Reviewed-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
next prev parent reply other threads:[~2025-09-08 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 10:20 [PATCH 0/2] GuC CT devm actions improvements Michal Wajdeczko
2025-09-08 10:20 ` [PATCH 1/2] drm/xe/guc: Always add CT disable action during second init step Michal Wajdeczko
2025-09-08 11:50 ` K V P, Satyanarayana
2025-09-08 10:20 ` [PATCH 2/2] drm/xe/guc: Don't invoke disable_ct action during replacement Michal Wajdeczko
2025-09-08 10:57 ` K V P, Satyanarayana [this message]
2025-09-08 22:05 ` ✓ CI.KUnit: success for GuC CT devm actions improvements Patchwork
2025-09-08 22:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-09 2:54 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-09 9:44 ` Michal Wajdeczko
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=2d7c2a72-2589-4e82-8aca-1c239711391e@intel.com \
--to=satyanarayana.k.v.p@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@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