Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Tauro, Riana" <riana.tauro@intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: <dri-devel@lists.freedesktop.org>,
	Matt Roper <matthew.d.roper@intel.com>,
	 Raag Jadav <raag.jadav@intel.com>
Subject: Re: [PATCH 1/1] drm/xe/survivability: broadcast dmesg when engaging survivability
Date: Mon, 2 Nov 2026 11:21:34 +0530	[thread overview]
Message-ID: <97194eeb-c204-483e-9945-e76db69b3fee@intel.com> (raw)
In-Reply-To: <20261030171738.674775-2-alan.previn.teres.alexis@intel.com>


On 30-10-2026 22:47, Alan Previn wrote:
> When user requests to enter survivabilty via configfs, or if
> check_boot_failure is hit inside xe_survivability_mode_is_requested,
> no indication is published. This patch adds some awareness in dmesg.
>
>   v3 : Limit message to xe_survivability_mode_is_requested. (Riana)
>   v2 : Remove / modify messages to reflect underlying behavior. (Sashiko)
>
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_survivability_mode.c | 10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_survivability_mode.c b/drivers/gpu/drm/xe/xe_survivability_mode.c
> index d73cdad0b3a9..344b402eb728 100644
> --- a/drivers/gpu/drm/xe/xe_survivability_mode.c
> +++ b/drivers/gpu/drm/xe/xe_survivability_mode.c
> @@ -413,13 +413,19 @@ bool xe_survivability_mode_is_requested(struct xe_device *xe)
>   
>   	survivability_mode = xe_configfs_get_survivability_mode(pdev);
>   	/* Enable survivability mode if set via configfs */
> -	if (survivability_mode)
> +	if (survivability_mode) {
> +		xe_log_info(xe, SURVIVABILITY, "Boot mode requested.");
>   		return true;
> +	}
>   
>   	data = xe_mmio_read32(mmio, PCODE_SCRATCH(0));
>   	survivability->boot_status = REG_FIELD_GET(BOOT_STATUS, data);
>   
> -	return check_boot_failure(xe);
> +	if (check_boot_failure(xe)) {
> +		xe_log_err_fatal(pdev, SURVIVABILITY, 0, "Boot Mode enabled!\n");
> +		return true;
> +	}
> +	return false;
>   }

Can we also remove logs from enable_boot_survivability_mode to avoid 
redundant logs.

Thanks
Riana

>   
>   /**
>
> base-commit: d8a353e238652bec29fd452babdaae0044d30b9b

  parent reply	other threads:[~2026-11-02  5:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 17:17 [PATCH 1/1] drm/xe/survivability: broadcast dmesg when engaging survivability Alan Previn
2026-10-30 17:24 ` sashiko-bot
2026-10-30 18:01 ` ✓ CI.KUnit: success for series starting with [1/1] " Patchwork
2026-10-30 18:36 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-31 13:49 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-11-02  5:51 ` Tauro, Riana [this message]
2026-11-02 19:33   ` [PATCH 1/1] " Teres Alexis, Alan Previn
  -- strict thread matches above, loose matches on Subject: below --
2026-11-02 22:26 Alan Previn
2026-11-02 22:33 ` sashiko-bot
2026-11-03  6:29 ` Tauro, Riana
2026-11-02 22:19 Alan Previn
2026-11-02 22:27 ` sashiko-bot
2026-10-23 17:36 Alan Previn
2026-10-28  3:18 ` Raag Jadav
2026-10-28 21:01   ` Teres Alexis, Alan Previn
2026-10-29  4:48     ` Raag Jadav
2026-10-29  9:38       ` Tauro, Riana
2026-10-29 18:41         ` Teres Alexis, Alan Previn
2026-10-29 18:57           ` Teres Alexis, Alan Previn
2026-10-23  0:18 Alan Previn
2026-10-23  0:27 ` sashiko-bot
2026-10-23 16:43   ` Teres Alexis, Alan Previn

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=97194eeb-c204-483e-9945-e76db69b3fee@intel.com \
    --to=riana.tauro@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=raag.jadav@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