Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-xe <intel-xe@lists.freedesktop.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Francois Dugast <francois.dugast@intel.com>,
	Riana Tauro <riana.tauro@intel.com>
Subject: [PATCH 0/2] drm/xe: Fix survivability
Date: Mon, 10 Mar 2025 22:35:15 -0700	[thread overview]
Message-ID: <20250310-fix-survivability-v1-0-7af31432bbd0@intel.com> (raw)

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().

Entering survivability mode was tested with an additional one line to
change the return of xe_survivability_mode_capable(). 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.

Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
Lucas De Marchi (2):
      drm/xe: Move survivability back to xe
      drm/xe: Allow to inject error in xe_pcode_probe_early()

 drivers/gpu/drm/xe/xe_device.c             | 14 +++++++++++++-
 drivers/gpu/drm/xe/xe_pci.c                | 16 +++++++---------
 drivers/gpu/drm/xe/xe_pcode.c              |  2 ++
 drivers/gpu/drm/xe/xe_survivability_mode.c | 14 +++++++++-----
 4 files changed, 31 insertions(+), 15 deletions(-)
---
base-commit: 003c44ec0b7d86569bd13d4a810ee24176c3d034
change-id: 20250310-fix-survivability-703246c0c480

Best regards,
-- 
Lucas De Marchi <lucas.demarchi@intel.com>


             reply	other threads:[~2025-03-11  5:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  5:35 Lucas De Marchi [this message]
2025-03-11  5:35 ` [PATCH 1/2] drm/xe: Move survivability back to xe Lucas De Marchi
2025-03-11  5:35 ` [PATCH 2/2] drm/xe: Allow to inject error in xe_pcode_probe_early() Lucas De Marchi
2025-03-11  5:40 ` ✓ CI.Patch_applied: success for drm/xe: Fix survivability Patchwork
2025-03-11  5:40 ` ✓ CI.checkpatch: " Patchwork
2025-03-11  5:42 ` ✓ CI.KUnit: " Patchwork
2025-03-11  5:58 ` ✓ CI.Build: " Patchwork
2025-03-11  6:00 ` ✓ CI.Hooks: " Patchwork
2025-03-11  6:02 ` ✓ CI.checksparse: " Patchwork
2025-03-11  6:22 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12  0:54 ` ✗ 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=20250310-fix-survivability-v1-0-7af31432bbd0@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=riana.tauro@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