From: Raag Jadav <raag.jadav@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe <intel-xe@lists.freedesktop.org>,
Francois Dugast <francois.dugast@intel.com>,
Riana Tauro <riana.tauro@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v4 0/3] drm/xe: Fix survivability
Date: Tue, 18 Mar 2025 17:50:57 +0200 [thread overview]
Message-ID: <Z9mWYboCcw2jgWq8@black.fi.intel.com> (raw)
In-Reply-To: <20250313-fix-survivability-v4-0-5e90efdede99@intel.com>
On Thu, Mar 13, 2025 at 01:40:58PM -0700, Lucas De Marchi wrote:
> It turns out commit d40f275d96e8 ("drm/xe: Move survivability entirely
> to xe_pci") did a bad job moving things to xe_pci. The fix provided by
> Riana in 20250306055407.511405-1-riana.tauro@intel.com fixes it
> partially, but injecting a failure in xe_pcode_probe_early still causes
> the kernel to give warnings/errors.
>
> Correct the course and better split what is done in xe_pci vs xe_device.
> This time, also add a patch to test we can handle errors in
> xe_pcode_probe_early() and other early probe functions.
>
> Entering survivability mode was tested with an additional one line to
> change the return of xe_survivability_mode_requested(). If we want to
> inject error, we'd need to change it's return type, but there's also
> another patch series to force it via configs, so this doesn't seem very
> important right now.
Not sure how much it helps our case, but still leaving it here in case
it turns out to be useful.
https://lore.kernel.org/r/0-v5-642aa0c94070+4447f-fwctl_jgg@nvidia.com
Raag
prev parent reply other threads:[~2025-03-18 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 20:40 [PATCH v4 0/3] drm/xe: Fix survivability Lucas De Marchi
2025-03-13 20:40 ` [PATCH v4 1/3] drm/xe: Move survivability back to xe Lucas De Marchi
2025-03-17 5:24 ` Riana Tauro
2025-03-13 20:41 ` [PATCH v4 2/3] drm/xe: Set survivability mode before heci init Lucas De Marchi
2025-03-13 20:41 ` [PATCH v4 3/3] drm/xe: Allow to inject error in early probe Lucas De Marchi
2025-03-13 20:48 ` ✓ CI.Patch_applied: success for drm/xe: Fix survivability (rev4) Patchwork
2025-03-13 20:48 ` ✓ CI.checkpatch: " Patchwork
2025-03-13 20:49 ` ✓ CI.KUnit: " Patchwork
2025-03-13 21:06 ` ✓ CI.Build: " Patchwork
2025-03-13 21:08 ` ✓ CI.Hooks: " Patchwork
2025-03-13 21:10 ` ✓ CI.checksparse: " Patchwork
2025-03-14 12:07 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-14 12:47 ` ✓ CI.Patch_applied: success for drm/xe: Fix survivability (rev6) Patchwork
2025-03-14 12:48 ` ✓ CI.checkpatch: " Patchwork
2025-03-14 12:49 ` ✓ CI.KUnit: " Patchwork
2025-03-14 13:19 ` ✓ CI.Build: " Patchwork
2025-03-14 13:21 ` ✓ CI.Hooks: " Patchwork
2025-03-14 13:23 ` ✓ CI.checksparse: " Patchwork
2025-03-14 13:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-14 20:45 ` ✓ Xe.CI.Full: " Patchwork
2025-03-18 15:50 ` Raag Jadav [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=Z9mWYboCcw2jgWq8@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=francois.dugast@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