From: Raag Jadav <raag.jadav@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com, aravind.iddamsetty@linux.intel.com,
badal.nilawar@intel.com, ravi.kishore.koppuravuri@intel.com,
mallesh.koujalagi@intel.com
Subject: Re: [PATCH 5/5] drm/xe/xe_ras: Add support to query error counter for CRI
Date: Wed, 1 Apr 2026 10:08:50 +0200 [thread overview]
Message-ID: <aczSkmVPPc8o0buN@black.igk.intel.com> (raw)
In-Reply-To: <20260320102607.1017511-6-riana.tauro@intel.com>
On Fri, Mar 20, 2026 at 03:56:00PM +0530, Riana Tauro wrote:
> Add support to query error counter for all errors.
>
> When userspace queries a DRM RAS error counter, fetch the
> latest value from system controller.
>
> Integrate this with XE DRM RAS.
>
> Example : query the counters using ynl
Either Usage or Example, let keep it consistent with other series.
> List all supported errors
>
> $ sudo ynl --family drm_ras --dump get-error-counter \
> --json '{"node-id":1}'
> [{"error-id": 1, "error-name": "core-compute", "error-value": 0},
> {"error-id": 2, "error-name": "soc-internal", "error-value": 0},
> {"error-id": 3, "error-name": "device-memory", "error-value": 0},
> {"error-id": 4, "error-name": "pcie", "error-value": 0},
> {"error-id": 5, "error-name": "fabric", "error-value": 0},]
I haven't tried this but do we really get the last comma in output?
...
> +/**
> + * xe_ras_get_error_counter() - Get error counter value
> + * @xe: xe device instance
> + * @severity: Error severity level to be queried
> + * @error_id: Error component to be queried
> + * @value: Counter value
> + *
> + * This function retrieves the value of a specific RAS error counter based on
> + * the provided severity and component.
> + *
> + * Return: 0 on success, negative error code on failure.
> + */
> +int xe_ras_get_error_counter(struct xe_device *xe, const enum drm_xe_ras_error_severity severity,
> + u32 error_id, u32 *value)
For event cases we need to reuse this based on error class we read,
perhaps keep a provision for it?
Raag
next prev parent reply other threads:[~2026-04-01 8:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 10:25 [PATCH 0/5] Add get-error-counter support for CRI Riana Tauro
2026-03-20 10:25 ` [PATCH 1/5] drm/xe/xe_sysctrl: Add System controller patch Riana Tauro
2026-03-20 10:25 ` [PATCH 2/5] drm/xe/uapi: Add additional error components to XE DRM RAS Riana Tauro
2026-03-25 9:24 ` Aravind Iddamsetty
2026-03-20 10:25 ` [PATCH 3/5] drm/xe/ras: Add flag for Xe RAS Riana Tauro
2026-04-01 7:53 ` Raag Jadav
2026-04-06 5:25 ` Tauro, Riana
2026-03-20 10:25 ` [PATCH 4/5] drm/xe/xe_ras: Add structures and commands for get counter Riana Tauro
2026-04-01 7:58 ` Raag Jadav
2026-04-06 5:23 ` Tauro, Riana
2026-04-07 7:45 ` Raag Jadav
2026-04-07 7:58 ` Tauro, Riana
2026-03-20 10:26 ` [PATCH 5/5] drm/xe/xe_ras: Add support to query error counter for CRI Riana Tauro
2026-04-01 8:08 ` Raag Jadav [this message]
2026-04-06 7:29 ` Tauro, Riana
2026-03-20 10:33 ` ✗ CI.checkpatch: warning for Add get-error-counter support " Patchwork
2026-03-20 10:35 ` ✓ CI.KUnit: success " Patchwork
2026-03-20 11:16 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-21 8:10 ` ✓ Xe.CI.FULL: success " 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=aczSkmVPPc8o0buN@black.igk.intel.com \
--to=raag.jadav@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=ravi.kishore.koppuravuri@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