From: Raag Jadav <raag.jadav@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Riana Tauro <riana.tauro@intel.com>,
intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
lucas.demarchi@intel.com
Subject: Re: [PATCH] drm/xe/xe_survivability: Add support for survivability mode v2
Date: Sun, 19 Oct 2025 17:55:04 +0200 [thread overview]
Message-ID: <aPUJ2JfS5UNFgMTH@black.igk.intel.com> (raw)
In-Reply-To: <aPFE4hIJKUKh1pjz@intel.com>
On Thu, Oct 16, 2025 at 03:17:54PM -0400, Rodrigo Vivi wrote:
> On Tue, Oct 14, 2025 at 11:02:58AM +0530, Riana Tauro wrote:
> > v2 survivability breadcrumbs introduces a new mode called
> > SPI Flash Descriptor Override mode (FDO). This is enabled by
> > PCODE when MEI itself fails and firmware cannot be updated via
> > MEI using igsc. This mode provides the ability to update
> > the firmware directly via SPI driver.
> >
> > Xe KMD initializes the nvm aux driver if FDO mode is enabled.
> >
> > Userspace should check FDO mode entry in survivability sysfs before
> > using the SPI driver to update firmware.
> >
> > v2 also supports survivability mode for critical boot errors.
> >
> > cat /sys/bus/pci/devices/0000\:03\:00.0/survivability_mode
> >
> > Capability Info: 0x138320 - 0x2001ae06
> > Postcode Info: 0x138324 - 0x0
> > Overflow Info: 0x138328 - 0x0
> > Auxiliary Info 0: 0x13832c - 0x0
>
> I am truly sorry here, but although I was the one that designed this,
> looking it now, I realized that this is breaking the sysfs rules
> of one value per file and no fancy format. This is only allowed in
> the debugfs.
>
> We need to change this asap, and with help from any tool that
> might be already consuming this.
>
> > FDO Mode: enabled
>
> After we fix that we can come and add this.
>
> About our options: I don't believe that debugfs is an option
> without the drm card right?
>
> Perhaps what we need is to transform survivability_mode in
> the directory. Each entry becomes a file in this directory.
>
> Sorry,
> Rodrigo.
Tried discussing in this direction[1], but not very convincingly I guess.
[1] https://lore.kernel.org/intel-xe/aIDrCMRK2gPGmIs6@black.fi.intel.com/
Raag
next prev parent reply other threads:[~2025-10-19 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 5:32 [PATCH] drm/xe/xe_survivability: Add support for survivability mode v2 Riana Tauro
2025-10-14 6:10 ` ✓ CI.KUnit: success for " Patchwork
2025-10-14 6:46 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-14 14:09 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-16 19:17 ` [PATCH] " Rodrigo Vivi
2025-10-19 15:55 ` Raag Jadav [this message]
2025-10-26 18:59 ` Raag Jadav
2025-10-22 12:38 ` Riana Tauro
2025-11-03 8:05 ` Riana Tauro
2025-11-04 18:16 ` 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=aPUJ2JfS5UNFgMTH@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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