Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Riana Tauro <riana.tauro@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: riana.tauro@intel.com, anshuman.gupta@intel.com,
	rodrigo.vivi@intel.com, aravind.iddamsetty@linux.intel.com,
	raag.jadav@intel.com, ravi.kishore.koppuravuri@intel.com,
	matthew.d.roper@intel.com
Subject: [PATCH 0/2] Xe Pci error handling fixes
Date: Fri, 28 Aug 2026 17:01:05 +0530	[thread overview]
Message-ID: <20260828113104.319843-4-riana.tauro@intel.com> (raw)

Wait for device to be ready by checking if pcode initialization is
complete before accessing device. Also do not access device in teardown
path in an unknown state.

Riana Tauro (2):
  drm/xe/xe_pci_error: Wait for device to be ready post reset
  drm/xe/xe_ras: Skip GuC reset post SBR

 drivers/gpu/drm/xe/xe_device.h    | 5 -----
 drivers/gpu/drm/xe/xe_guc.c       | 5 +++++
 drivers/gpu/drm/xe/xe_pci_error.c | 6 +++++-
 3 files changed, 10 insertions(+), 6 deletions(-)

-- 
2.47.1


             reply	other threads:[~2026-08-28 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 11:31 Riana Tauro [this message]
2026-08-28 11:31 ` [PATCH 1/2] drm/xe/xe_pci_error: Wait for pcode init post SBR Riana Tauro
2026-08-28 11:41   ` sashiko-bot
2026-08-28 14:06   ` Gupta, Anshuman
2026-08-29 14:00     ` Raag Jadav
2026-08-31 12:32     ` Aravind Iddamsetty
2026-09-03 12:53       ` Gupta, Anshuman
2026-08-28 11:31 ` [PATCH 2/2] drm/xe/xe_guc: Skip GuC reset " Riana Tauro
2026-08-28 11:44   ` sashiko-bot
2026-09-03 16:34   ` Teres Alexis, Alan Previn
2026-08-28 11:38 ` ✓ CI.KUnit: success for Xe Pci error handling fixes Patchwork
2026-08-28 12:21 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-28 13:30 ` ✓ Xe.CI.FULL: " 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=20260828113104.319843-4-riana.tauro@intel.com \
    --to=riana.tauro@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=raag.jadav@intel.com \
    --cc=ravi.kishore.koppuravuri@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