From: "Tauro, Riana" <riana.tauro@intel.com>
To: Raag Jadav <raag.jadav@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <michal.wajdeczko@intel.com>, <matthew.d.roper@intel.com>,
<mallesh.koujalagi@intel.com>
Subject: Re: [PATCH v2] drm/xe/pci_error: Allow debugging PCI errors
Date: Wed, 19 Aug 2026 16:14:37 +0530 [thread overview]
Message-ID: <effa9774-baeb-4f92-a83e-380279552b9c@intel.com> (raw)
In-Reply-To: <20260818103050.493252-1-raag.jadav@intel.com>
On 18-08-2026 16:00, Raag Jadav wrote:
> XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET is intended for debugging hangs.
> Disconnect the device on AER and prevent bus reset, so that it is available
> to the user for debugging.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> v2: Process errors before wedging (Riana)
> ---
Sorry RB was meant for v2 not v1. Please ignore the first response
Please rephrase this according to sashiko suggestion.
With that fixed, v2 looks good to me
Reviewed-by: Riana Tauro <riana.tauro@intel.com>
> drivers/gpu/drm/xe/xe_pci_error.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_pci_error.c b/drivers/gpu/drm/xe/xe_pci_error.c
> index fb965f52be5e..79ce0c671549 100644
> --- a/drivers/gpu/drm/xe/xe_pci_error.c
> +++ b/drivers/gpu/drm/xe/xe_pci_error.c
> @@ -84,6 +84,12 @@ static pci_ers_result_t xe_pci_error_mmio_enabled(struct pci_dev *pdev)
> xe_info(xe, "PCI error: MMIO enabled\n");
> action = xe_ras_process_errors(xe);
>
> + /* User wants to debug the error, prevent reset */
> + if (xe->wedged.mode == XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET) {
> + xe_device_declare_wedged(xe);
> + return PCI_ERS_RESULT_DISCONNECT;
> + }
> +
> return ras_action_to_pci_result(pdev, action);
> }
>
prev parent reply other threads:[~2026-08-19 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 10:30 [PATCH v2] drm/xe/pci_error: Allow debugging PCI errors Raag Jadav
2026-08-18 10:39 ` ✓ CI.KUnit: success for drm/xe/pci_error: Allow debugging PCI errors (rev2) Patchwork
2026-08-18 10:42 ` [PATCH v2] drm/xe/pci_error: Allow debugging PCI errors sashiko-bot
2026-08-18 12:31 ` ✓ CI.KUnit: success for drm/xe/pci_error: Allow debugging PCI errors (rev3) Patchwork
2026-08-18 13:05 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-18 14:41 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-08-19 10:44 ` Tauro, Riana [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=effa9774-baeb-4f92-a83e-380279552b9c@intel.com \
--to=riana.tauro@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@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