From: sashiko-bot@kernel.org
To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v14 17/17] drm/xe/vsec: Support survivability mode for CRI
Date: Tue, 10 Nov 2026 18:53:30 +0000 [thread overview]
Message-ID: <sashiko-outbox-207617@kernel.org> (raw)
In-Reply-To: <20261110183505.694124-36-michael.j.ruhl@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/xe/vsec: use xe_survivability_mode_is_boot_enabled() instead
of pmt cache
--
commit c58d99d8bdca0b8d22ebde50d5dc7b64549279f1
Author: Michael J. Ruhl <michael.j.ruhl@intel.com>
drm/xe/vsec: Support survivability mode for CRI
This commit adds a VSEC configuration for Crescent Island in survivability
mode that exposes only the PUNIT crashlog PMT capability.
> diff --git a/drivers/gpu/drm/xe/xe_device_types.h b/drivers/gpu/drm/xe/xe_device_types.h
> index a35a8b6e733e5..5d4548d863761 100644
> --- a/drivers/gpu/drm/xe/xe_device_types.h
> +++ b/drivers/gpu/drm/xe/xe_device_types.h
> @@ -492,6 +492,8 @@ struct xe_device {
> u32 retry_count;
> /** @pmt.punit_guid_cache: cache of the PUNIT GUID */
> u32 punit_guid_cache;
> + /** @pmt.survivability_mode: cache of survivability mode state */
> + bool survivability_mode;
> } pmt;
>
> /** @soc_remapper: SoC remapper object */
> diff --git a/drivers/gpu/drm/xe/xe_vsec.c b/drivers/gpu/drm/xe/xe_vsec.c
> index f27bfe8218d78..ffaed9ef43b25 100644
> --- a/drivers/gpu/drm/xe/xe_vsec.c
> +++ b/drivers/gpu/drm/xe/xe_vsec.c
[ ... ]
> @@ -319,7 +339,7 @@ static bool wait_for_fw(struct xe_device *xe)
> {
> int retries = VSEC_LATE_BIND_RETRY; /* wait up to 20 secs */
>
> - if (xe->info.platform != XE_CRESCENTISLAND)
> + if (xe->info.platform != XE_CRESCENTISLAND || xe->pmt.survivability_mode)
> return true;
>
> while (retries--) {
> @@ -538,6 +558,8 @@ static const int vsec_platforms[] = {
>
> static enum xe_vsec get_platform_info(struct xe_device *xe)
> {
> + struct xe_survivability *survivability = &xe->survivability;
> +
> if (xe->info.platform > XE_CRESCENTISLAND)
> return XE_VSEC_UNKNOWN;
>
> @@ -546,6 +568,9 @@ static enum xe_vsec get_platform_info(struct xe_device *xe)
> xe->info.platform == XE_CRESCENTISLAND))
> return XE_VSEC_UNKNOWN;
>
> + if (survivability->mode && xe->info.platform == XE_CRESCENTISLAND)
> + return XE_VSEC_CRI_SURVIVABILITY;
> +
> return vsec_platforms[xe->info.platform];
> }
>
> @@ -686,6 +711,13 @@ int xe_vsec_init(struct xe_device *xe)
> xe->soc_remapper.set_telem_region(xe, CRI_IDX_TELEM_DISCOVERY);
> break;
>
> + case XE_VSEC_CRI_SURVIVABILITY:
> + xe->pmt.base_offset = CRI_PMT_OFFSET;
> + xe->pmt.survivability_mode = true;
> + info->priv_data = &xe_cri_pmt_cb;
> + xe->soc_remapper.set_telem_region(xe, CRI_IDX_TELEM_DISCOVERY);
> + break;
[Severity: Low]
Could wait_for_fw() and get_platform_info() call
xe_survivability_mode_is_boot_enabled(xe) directly instead of reaching into
xe->survivability.mode and caching it in xe->pmt.survivability_mode? Other
subsystems (such as xe_pci.c, xe_heci_gsc.c and xe_i2c.c) already use that
helper, which would also avoid adding the duplicate boolean to struct
xe_device.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110183505.694124-19-michael.j.ruhl@intel.com?part=17
next prev parent reply other threads:[~2026-11-10 18:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 18:35 [PATCH v14 00/17] Crescent Island PMT support Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 01/17] drm/xe/vsec: VSEC requires soc-remapper Michael J. Ruhl
2026-11-10 18:46 ` sashiko-bot
2026-11-10 18:35 ` [PATCH v14 02/17] drm/xe/vsec: Do not register BMG PMT for VF Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 03/17] drm/xe/vsec: Correct locking order Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 04/17] drm/xe/vsec: Use correct pm state get Michael J. Ruhl
2026-11-10 18:49 ` sashiko-bot
2026-11-10 18:35 ` [PATCH v14 05/17] drm/xe/vsec: Add DOC text for VSEC Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 06/17] drm/xe/vsec: Support possible hotplug exit Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 07/17] drm/xe/vsec: Refactor BattleMage PMT defines Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 08/17] drm/xe/vsec: Update VSEC probe order Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 09/17] drm/xe/vsec: Add base_offset to allow for more flexibilty Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 10/17] drm/xe/vsec: Support Crescent Island PMT Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 11/17] drm/xe/vsec: Crescent Island PMT decode Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 12/17] drm/xe/vsec: Crescent Island PMT callbacks Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 13/17] drm/xe/vsec: Support late bind fw information Michael J. Ruhl
2026-11-10 19:08 ` sashiko-bot
2026-11-10 18:35 ` [PATCH v14 14/17] drm/xe/vsec: Add PMT GUID internal access Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 15/17] drm/xe/vsec: Update PMT " Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 16/17] drm/xe/vsec: Refactor platform check Michael J. Ruhl
2026-11-10 18:35 ` [PATCH v14 17/17] drm/xe/vsec: Support survivability mode for CRI Michael J. Ruhl
2026-11-10 18:53 ` sashiko-bot [this message]
2026-11-10 18:42 ` ✗ CI.checkpatch: warning for Crescent Island PMT support (rev16) Patchwork
2026-11-10 18:44 ` ✓ CI.KUnit: success " Patchwork
2026-11-10 19:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-10 21:19 ` ✗ 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=sashiko-outbox-207617@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michael.j.ruhl@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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