From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Skip pxp init if gt is wedged
Date: Fri, 27 Oct 2023 10:13:54 +0300 [thread overview]
Message-ID: <87a5s47d1p.fsf@intel.com> (raw)
In-Reply-To: <20231026215444.54880-1-zhanjun.dong@intel.com>
On Thu, 26 Oct 2023, Zhanjun Dong <zhanjun.dong@intel.com> wrote:
> gt wedged is fatal error, skip the pxp init on this situation.
More information is needed in the commit message. When do you encounter
this situation?
I'll note that nobody checks intel_pxp_init() return status, so this
silently skips PXP.
BR,
Jani.
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> ---
> drivers/gpu/drm/i915/pxp/intel_pxp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/pxp/intel_pxp.c b/drivers/gpu/drm/i915/pxp/intel_pxp.c
> index dc327cf40b5a..923f233c91e1 100644
> --- a/drivers/gpu/drm/i915/pxp/intel_pxp.c
> +++ b/drivers/gpu/drm/i915/pxp/intel_pxp.c
> @@ -212,6 +212,9 @@ int intel_pxp_init(struct drm_i915_private *i915)
> if (!gt)
> return -ENODEV;
>
> + if (intel_gt_is_wedged(gt))
> + return -ENODEV;
> +
> /*
> * At this point, we will either enable full featured PXP capabilities
> * including session and object management, or we will init the backend tee
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-27 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 21:54 [Intel-gfx] [PATCH] drm/i915: Skip pxp init if gt is wedged Zhanjun Dong
2023-10-27 6:40 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-10-27 7:13 ` Jani Nikula [this message]
2023-10-31 21:38 ` [Intel-gfx] [PATCH] " Teres Alexis, Alan Previn
2023-11-01 17:57 ` Dong, Zhanjun
2023-10-28 17:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 21:44 [Intel-gfx] [PATCH] " Zhanjun Dong
2023-11-03 15:45 ` Rodrigo Vivi
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=87a5s47d1p.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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