From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>, intel-xe@lists.freedesktop.org
Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>,
Stuart Summers <stuart.summers@intel.com>
Subject: Re: [PATCH v6] drm/xe/uc: Disable GuC communication on hardware initialization error.
Date: Tue, 24 Jun 2025 22:15:14 +0200 [thread overview]
Message-ID: <4715fb2c-8176-4ace-a56c-e6dfc2da08c6@intel.com> (raw)
In-Reply-To: <20250624011735.3976-1-zhanjun.dong@intel.com>
On 24.06.2025 03:17, Zhanjun Dong wrote:
> Disable GuC communication on Xe micro controller hardware initialization
> error.
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4917
>
> ---
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Stuart Summers <stuart.summers@intel.com>
> Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
>
> Change list:
> v6: Skip disable ct on xe_guc_enable_communication error
> v5: Set wedge is excessive action, revert back to disable ct
> v4: Fix typo and add new line
> v3: v2 CI re-run
> v2: Remove unnecessary jump to err-out
> Drop disable ct, switch to set wedge
> ---
> drivers/gpu/drm/xe/xe_guc.c | 5 +++++
> drivers/gpu/drm/xe/xe_guc.h | 1 +
> drivers/gpu/drm/xe/xe_uc.c | 19 ++++++++++++++-----
> 3 files changed, 20 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 209e5d53c290..9d7175b16cc7 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -1230,6 +1230,11 @@ int xe_guc_enable_communication(struct xe_guc *guc)
> return 0;
> }
>
each new public function needs to have a proper kernel-doc
> +void xe_guc_disable_communication(struct xe_guc *guc)
> +{
> + xe_guc_ct_disable(&guc->ct);
> +}
> +
> int xe_guc_suspend(struct xe_guc *guc)
> {
> struct xe_gt *gt = guc_to_gt(guc);
> diff --git a/drivers/gpu/drm/xe/xe_guc.h b/drivers/gpu/drm/xe/xe_guc.h
> index 58338be44558..285c19929f8c 100644
> --- a/drivers/gpu/drm/xe/xe_guc.h
> +++ b/drivers/gpu/drm/xe/xe_guc.h
> @@ -33,6 +33,7 @@ int xe_guc_reset(struct xe_guc *guc);
> int xe_guc_upload(struct xe_guc *guc);
> int xe_guc_min_load_for_hwconfig(struct xe_guc *guc);
> int xe_guc_enable_communication(struct xe_guc *guc);
> +void xe_guc_disable_communication(struct xe_guc *guc);
> int xe_guc_suspend(struct xe_guc *guc);
> void xe_guc_notify(struct xe_guc *guc);
> int xe_guc_auth_huc(struct xe_guc *guc, u32 rsa_addr);
> diff --git a/drivers/gpu/drm/xe/xe_uc.c b/drivers/gpu/drm/xe/xe_uc.c
> index 3a8751a8b92d..d74bfc7a85d1 100644
> --- a/drivers/gpu/drm/xe/xe_uc.c
> +++ b/drivers/gpu/drm/xe/xe_uc.c
> @@ -13,6 +13,7 @@
> #include "xe_gt_printk.h"
> #include "xe_gt_sriov_vf.h"
> #include "xe_guc.h"
> +#include "xe_guc_ct.h"
> #include "xe_guc_pc.h"
> #include "xe_guc_engine_activity.h"
> #include "xe_huc.h"
> @@ -161,15 +162,19 @@ static int vf_uc_init_hw(struct xe_uc *uc)
>
> err = xe_gt_sriov_vf_connect(uc_to_gt(uc));
> if (err)
> - return err;
> + goto err_out;
>
> uc->guc.submission_state.enabled = true;
>
> err = xe_gt_record_default_lrcs(uc_to_gt(uc));
> if (err)
> - return err;
> + goto err_out;
>
> return 0;
> +
> +err_out:
> + xe_guc_disable_communication(&uc->guc);
> + return err;
> }
>
> /*
> @@ -201,15 +206,15 @@ int xe_uc_init_hw(struct xe_uc *uc)
>
> ret = xe_gt_record_default_lrcs(uc_to_gt(uc));
> if (ret)
> - return ret;
> + goto err_out;
>
> ret = xe_guc_post_load_init(&uc->guc);
> if (ret)
> - return ret;
> + goto err_out;
>
> ret = xe_guc_pc_start(&uc->guc.pc);
> if (ret)
> - return ret;
> + goto err_out;
>
> xe_guc_engine_activity_enable_stats(&uc->guc);
>
> @@ -221,6 +226,10 @@ int xe_uc_init_hw(struct xe_uc *uc)
> xe_gsc_load_start(&uc->gsc);
>
> return 0;
> +
> +err_out:
> + xe_guc_disable_communication(&uc->guc);
> + return ret;
> }
>
> int xe_uc_fini_hw(struct xe_uc *uc)
what about doing similar cleanup in xe_guc_min_load_for_hwconfig() where
we also have unbalanced xe_guc_enable_communication() ?
next prev parent reply other threads:[~2025-06-24 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 1:17 [PATCH v6] drm/xe/uc: Disable GuC communication on hardware initialization error Zhanjun Dong
2025-06-24 1:24 ` ✓ CI.KUnit: success for drm/xe/uc: Disable GuC communication on hardware initialization error. (rev3) Patchwork
2025-06-24 5:22 ` ✓ CI.KUnit: success for drm/xe/uc: Disable GuC communication on hardware initialization error. (rev4) Patchwork
2025-06-24 6:50 ` ✗ Xe.CI.Full: failure for drm/xe/uc: Disable GuC communication on hardware initialization error. (rev3) Patchwork
2025-06-24 7:31 ` ✗ Xe.CI.Full: failure for drm/xe/uc: Disable GuC communication on hardware initialization error. (rev4) Patchwork
2025-06-24 20:15 ` Michal Wajdeczko [this message]
2025-06-24 22:17 ` [PATCH v6] drm/xe/uc: Disable GuC communication on hardware initialization error Cavitt, Jonathan
2025-06-30 18:52 ` Dong, Zhanjun
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=4715fb2c-8176-4ace-a56c-e6dfc2da08c6@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=stuart.summers@intel.com \
--cc=zhanjun.dong@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