From: "Tauro, Riana" <riana.tauro@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
"Jadav, Raag" <raag.jadav@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Gupta, Anshuman" <anshuman.gupta@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"aravind.iddamsetty@linux.intel.com"
<aravind.iddamsetty@linux.intel.com>,
"Nilawar, Badal" <badal.nilawar@intel.com>,
"Koppuravuri, Ravi Kishore" <ravi.kishore.koppuravuri@intel.com>,
"Koujalagi, Mallesh" <mallesh.koujalagi@intel.com>,
"Purkait, Soham" <soham.purkait@intel.com>
Subject: Re: [PATCH v4 06/13] drm/xe/xe_ras: Add basic structures and commands for uncorrectable errors
Date: Mon, 20 Apr 2026 11:04:40 +0530 [thread overview]
Message-ID: <02b7cd96-73c3-4fb8-922b-afbb8fa4d27f@intel.com> (raw)
In-Reply-To: <20260417213235.GG7476@mdroper-desk1.amr.corp.intel.com>
On 4/18/2026 3:02 AM, Matt Roper wrote:
> On Fri, Apr 17, 2026 at 02:25:28PM -0700, Jadav, Raag wrote:
>>
>>> -----Original Message-----
>>> From: Roper, Matthew D <matthew.d.roper@intel.com>
>>> On Fri, Apr 17, 2026 at 02:28:18PM +0530, Riana Tauro wrote:
>>>> Add the commands and common structures for the get_soc_error
>>>> sysctrl command.
>> ...
>>
>>>> +/* Severity classification of detected errors */
>>>> +enum xe_ras_severity {
>>>> + XE_RAS_SEVERITY_NOT_SUPPORTED = 0,
>>>> + XE_RAS_SEVERITY_CORRECTABLE,
>>>> + XE_RAS_SEVERITY_UNCORRECTABLE,
>>>> + XE_RAS_SEVERITY_INFORMATIONAL,
>>>> + XE_RAS_SEVERITY_MAX
>>>> +};
>>> Drive-by comment: I notice that there's a fair amount of common changes
>>> between this uncorrectable series and Raag's correctable series, e.g.,
>>> https://lore.kernel.org/all/20260410102744.427150-4-raag.jadav@intel.com/
>>> However it seems that there have been some minor style differences
>>> between the two that would be good to reconcile (e.g., this series
>>> writes out the full XE_RAS_SEVERITY_*, XE_RAS_COMPONENT_*, etc.
>>> whereas
>>> Raag's series uses slightly shorter XE_RAS_SEV_*, XE_RAS_COMP_*, etc.
>>> names). Similar differences exist on some of the functions like
>>> severity_to_string (taking both the device and the severity) here vs
>>> sev_to_string (taking only the serverity) in the other series.
>>>
>>> We should probably figure out which form we actually want to go with so
>>> that we don't have last-minute conflicts as we start applying these
>>> series.
>> The one's in my series are consistent with uapi, but I'm okay with
>> either one. My only concern is that we don't invent overly long names
>> that warrant ugly wrapping while using them in the code.
> Yeah, I don't have any strong feelings one way or the other. But if I
> want to apply both your series and Riana's series to the same branch for
> tracking or testing, I'm left uncertain which series I should favor on
> the conflict resolutions. It would be good if we could come to a
> decision early just so the two series don't drift apart.
>
Yeah using the full word here wasn't creating longer names so i
preferred it over abbrevations.
I will make the patch in-line with Raag's patch in the next rev.
His series has got all RB's so might land before this series.
Riana
>
> Are we expecting one of these series to land before the other, or do
> expect both RAS sets to land together?
>
>
> Matt
>
>> Raag
>>
next prev parent reply other threads:[~2026-04-20 5:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:58 [PATCH v4 00/13] Introduce Xe Uncorrectable Error Handling Riana Tauro
2026-04-17 8:58 ` [PATCH v4 01/13] drm/xe/xe_survivability: Decouple survivability info from boot survivability Riana Tauro
2026-04-17 8:58 ` [PATCH v4 02/13] drm/xe/xe_pci_error: Implement PCI error recovery callbacks Riana Tauro
2026-04-27 6:35 ` Raag Jadav
2026-04-17 8:58 ` [PATCH v4 03/13] drm/xe/xe_pci_error: Group all devres to release them on PCIe slot reset Riana Tauro
2026-04-17 8:58 ` [PATCH v4 04/13] drm/xe: Skip device access during PCI error recovery Riana Tauro
2026-04-17 8:58 ` [PATCH v4 05/13] drm/xe/xe_ras: Initialize Uncorrectable AER Registers Riana Tauro
2026-04-27 7:56 ` Raag Jadav
2026-04-17 8:58 ` [PATCH v4 06/13] drm/xe/xe_ras: Add basic structures and commands for uncorrectable errors Riana Tauro
2026-04-17 17:38 ` Matt Roper
2026-04-17 21:25 ` Jadav, Raag
2026-04-17 21:32 ` Matt Roper
2026-04-20 5:34 ` Tauro, Riana [this message]
2026-04-20 7:49 ` Raag Jadav
2026-04-17 8:58 ` [PATCH v4 07/13] drm/xe/xe_ras: Add support for uncorrectable core-compute errors Riana Tauro
2026-04-27 8:24 ` Raag Jadav
2026-04-17 8:58 ` [PATCH v4 08/13] drm/xe/xe_ras: Handle uncorrectable SoC Internal errors Riana Tauro
2026-04-17 8:58 ` [PATCH v4 09/13] drm/xe/xe_ras: Handle uncorrectable device memory errors Riana Tauro
2026-04-21 6:08 ` Upadhyay, Tejas
2026-04-17 8:58 ` [PATCH v4 10/13] drm/xe/xe_ras: Add support to offline/decline a page Riana Tauro
2026-04-21 6:21 ` Upadhyay, Tejas
2026-04-17 8:58 ` [PATCH v4 11/13] drm/xe/xe_ras: Add support for page offline list and queue commands Riana Tauro
2026-04-21 6:19 ` Upadhyay, Tejas
2026-04-21 9:10 ` Upadhyay, Tejas
2026-04-17 8:58 ` [PATCH v4 12/13] drm/xe/xe_ras: Query errors from system controller on probe Riana Tauro
2026-04-28 11:46 ` Raag Jadav
2026-04-17 8:58 ` [PATCH v4 13/13] drm/xe/xe_pci_error: Process errors in mmio_enabled Riana Tauro
2026-04-28 11:39 ` Raag Jadav
2026-04-20 13:33 ` ✗ CI.checkpatch: warning for Introduce Xe Uncorrectable Error Handling (rev4) Patchwork
2026-04-20 13:35 ` ✓ CI.KUnit: success " Patchwork
2026-04-20 14:42 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-20 17:14 ` ✗ 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=02b7cd96-73c3-4fb8-922b-afbb8fa4d27f@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=raag.jadav@intel.com \
--cc=ravi.kishore.koppuravuri@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=soham.purkait@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