From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Soham Purkait <soham.purkait@intel.com>,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<badal.nilawar@intel.com>, <matthew.d.roper@intel.com>,
<riana.tauro@intel.com>
Subject: Re: [PATCH] drm/xe/survivability: Do not call xe_vsec_init() in boot survivability path
Date: Tue, 13 Oct 2026 14:56:38 -0400 [thread overview]
Message-ID: <as5-5v1r-oArbrZ2@intel.com> (raw)
In-Reply-To: <20261007100259.2661003-2-soham.purkait@intel.com>
On Wed, Oct 07, 2026 at 03:33:00PM +0530, Soham Purkait wrote:
> Boot survivability mode exists only for device recovery and firmware
> flashing. It does not need PMT/telemetry. Since xe_vsec_init() only
> sets up VSEC/PMT, there is no reason to call it on the boot survivability
> path.
>
> Signed-off-by: Soham Purkait <soham.purkait@intel.com>
Cc: Michael J. Ruhl <michael.j.ruhl@intel.com>
> ---
> drivers/gpu/drm/xe/xe_survivability_mode.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_survivability_mode.c b/drivers/gpu/drm/xe/xe_survivability_mode.c
> index 45d44ebe288b..f5985938c60b 100644
> --- a/drivers/gpu/drm/xe/xe_survivability_mode.c
> +++ b/drivers/gpu/drm/xe/xe_survivability_mode.c
> @@ -351,8 +351,6 @@ static int enable_boot_survivability_mode(struct pci_dev *pdev)
>
> xe_heci_gsc_init(xe);
>
> - xe_vsec_init(xe);
> -
> if (survivability->fdo_mode) {
> ret = xe_nvm_init(xe);
> if (ret)
> --
> 2.43.0
>
prev parent reply other threads:[~2026-10-13 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:03 [PATCH] drm/xe/survivability: Do not call xe_vsec_init() in boot survivability path Soham Purkait
2026-10-07 10:12 ` ✓ CI.KUnit: success for " Patchwork
2026-10-07 10:56 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-07 12:50 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-10-13 18:56 ` Rodrigo Vivi [this message]
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=as5-5v1r-oArbrZ2@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=riana.tauro@intel.com \
--cc=soham.purkait@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