From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
Cc: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v3 2/4] drm/xe/guc: Ignore GuC CT errors when wedged
Date: Tue, 3 Jun 2025 17:34:57 +0000 [thread overview]
Message-ID: <11b5e74326ea99b8d809e5018621bbbf3383b6df.camel@intel.com> (raw)
In-Reply-To: <20250602234415.2015921-3-vinay.belgaumkar@intel.com>
On Mon, 2025-06-02 at 16:44 -0700, Vinay Belgaumkar wrote:
> Messaging to GuC may get canceled when device is wedged. Don't
> flag this as an error in xe_guc_pc code.
So if we're wedged already we are already in an error state right? I
can understand flagging additional errors maybe gives a false negative,
or rather would prompt us to look at the earlier errors to make sure
these aren't just cascading, but do we really need to check for this?
Thanks,
Stuart
>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_pc.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c
> b/drivers/gpu/drm/xe/xe_guc_pc.c
> index cb0563494fcc..793df3486d1f 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
> @@ -154,7 +154,7 @@ static int pc_action_reset(struct xe_guc_pc *pc)
> int ret;
>
> ret = xe_guc_ct_send(ct, action, ARRAY_SIZE(action), 0, 0);
> - if (ret)
> + if (ret && !(xe_device_wedged(pc_to_xe(pc)) && ret == -
> ECANCELED))
> xe_gt_err(pc_to_gt(pc), "GuC PC reset failed: %pe\n",
> ERR_PTR(ret));
>
> @@ -178,7 +178,7 @@ static int pc_action_query_task_state(struct
> xe_guc_pc *pc)
>
> /* Blocking here to ensure the results are ready before
> reading them */
> ret = xe_guc_ct_send_block(ct, action, ARRAY_SIZE(action));
> - if (ret)
> + if (ret && !(xe_device_wedged(pc_to_xe(pc)) && ret == -
> ECANCELED))
> xe_gt_err(pc_to_gt(pc), "GuC PC query task state
> failed: %pe\n",
> ERR_PTR(ret));
>
> @@ -201,7 +201,7 @@ static int pc_action_set_param(struct xe_guc_pc
> *pc, u8 id, u32 value)
> return -EAGAIN;
>
> ret = xe_guc_ct_send(ct, action, ARRAY_SIZE(action), 0, 0);
> - if (ret)
> + if (ret && !(xe_device_wedged(pc_to_xe(pc)) && ret == -
> ECANCELED))
> xe_gt_err(pc_to_gt(pc), "GuC PC set param[%u]=%u
> failed: %pe\n",
> id, value, ERR_PTR(ret));
>
> @@ -223,7 +223,7 @@ static int pc_action_unset_param(struct xe_guc_pc
> *pc, u8 id)
> return -EAGAIN;
>
> ret = xe_guc_ct_send(ct, action, ARRAY_SIZE(action), 0, 0);
> - if (ret)
> + if (ret && !(xe_device_wedged(pc_to_xe(pc)) && ret == -
> ECANCELED))
> xe_gt_err(pc_to_gt(pc), "GuC PC unset param failed:
> %pe",
> ERR_PTR(ret));
>
> @@ -240,7 +240,7 @@ static int pc_action_setup_gucrc(struct xe_guc_pc
> *pc, u32 mode)
> int ret;
>
> ret = xe_guc_ct_send(ct, action, ARRAY_SIZE(action), 0, 0);
> - if (ret)
> + if (ret && !(xe_device_wedged(pc_to_xe(pc)) && ret == -
> ECANCELED))
> xe_gt_err(pc_to_gt(pc), "GuC RC enable mode=%u
> failed: %pe\n",
> mode, ERR_PTR(ret));
> return ret;
next prev parent reply other threads:[~2025-06-03 17:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 23:44 [PATCH v3 0/4] drm/xe/bmg: Update some WAs Vinay Belgaumkar
2025-06-02 23:44 ` [PATCH v3 1/4] drm/xe/bmg: Update Wa_14022085890 Vinay Belgaumkar
2025-06-03 17:36 ` Summers, Stuart
2025-06-03 18:41 ` Belgaumkar, Vinay
2025-06-03 19:31 ` Summers, Stuart
2025-06-03 20:31 ` Belgaumkar, Vinay
2025-06-04 0:06 ` Summers, Stuart
2025-06-07 0:09 ` Lucas De Marchi
2025-06-11 22:44 ` Summers, Stuart
2025-06-11 23:02 ` Lucas De Marchi
2025-06-11 23:31 ` Summers, Stuart
2025-06-12 6:49 ` Lucas De Marchi
2025-06-02 23:44 ` [PATCH v3 2/4] drm/xe/guc: Ignore GuC CT errors when wedged Vinay Belgaumkar
2025-06-03 17:34 ` Summers, Stuart [this message]
2025-06-03 18:42 ` Belgaumkar, Vinay
2025-06-04 0:09 ` Summers, Stuart
2025-06-07 0:10 ` Lucas De Marchi
2025-06-02 23:44 ` [PATCH v3 3/4] drm/xe/bmg: Update Wa_22019338487 Vinay Belgaumkar
2025-06-05 4:18 ` Nilawar, Badal
2025-06-07 0:09 ` Lucas De Marchi
2025-06-02 23:44 ` [PATCH v3 4/4] drm/xe/bmg: Update Wa_16023588340 Vinay Belgaumkar
2025-06-02 23:53 ` ✓ CI.Patch_applied: success for drm/xe/bmg: Update some WAs (rev3) Patchwork
2025-06-02 23:53 ` ✓ CI.checkpatch: " Patchwork
2025-06-02 23:54 ` ✓ CI.KUnit: " Patchwork
2025-06-03 0:05 ` ✓ CI.Build: " Patchwork
2025-06-03 0:07 ` ✓ CI.Hooks: " Patchwork
2025-06-03 0:08 ` ✓ CI.checksparse: " Patchwork
2025-06-03 0:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-04 3:36 ` ✗ Xe.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=11b5e74326ea99b8d809e5018621bbbf3383b6df.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=vinay.belgaumkar@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