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, soham.purkait@intel.com
Subject: Re: [PATCH v3 2/5] drm/xe/xe_ras: Add support to get error counter in CRI
Date: Thu, 23 Apr 2026 12:51:12 +0200 [thread overview]
Message-ID: <aen5oJTmbeQuNi4_@black.igk.intel.com> (raw)
In-Reply-To: <20260421145056.253300-9-riana.tauro@intel.com>
On Tue, Apr 21, 2026 at 08:20:58PM +0530, Riana Tauro wrote:
> Add request/response structures and helper functions to query system
> controller to get error counter value.
...
> +/**
> + * 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, enum drm_xe_ras_error_severity severity,
xe_ras_get_counter()? Pretty please.
> + u32 error_id, u32 *value)
> +{
> + struct xe_ras_error_class error_class = {0};
> +
> + error_class.common.severity = drm_to_xe_ras_severity[severity];
> + error_class.common.component = drm_to_xe_ras_component[error_id];
> +
> + guard(xe_pm_runtime)(xe);
> + return get_error_counter(xe, &error_class, value);
> +}
...
> +++ b/drivers/gpu/drm/xe/xe_ras_types.h
> @@ -0,0 +1,92 @@
> +/* SPDX-License-Identifier: MIT */
> +/*
> + * Copyright © 2026 Intel Corporation
> + */
> +
> +#ifndef _XE_RAS_TYPES_H_
> +#define _XE_RAS_TYPES_H_
> +
> +#include <linux/types.h>
> +
> +#define XE_RAS_INFO_QUEUE_MAX_CHUNK_SIZE 200
Any users?
Raag
next prev parent reply other threads:[~2026-04-23 10:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 14:50 [PATCH v3 0/5] Add get-error-counter and clear-error-counter support for CRI Riana Tauro
2026-04-21 14:26 ` ✗ CI.checkpatch: warning for Add get-error-counter and clear-error-counter support for CRI (rev2) Patchwork
2026-04-21 14:27 ` ✓ CI.KUnit: success " Patchwork
2026-04-21 14:50 ` [PATCH v3 1/5] drm/xe/uapi: Add additional error components to XE drm_ras Riana Tauro
2026-04-21 14:50 ` [PATCH v3 2/5] drm/xe/xe_ras: Add support to get error counter in CRI Riana Tauro
2026-04-23 10:51 ` Raag Jadav [this message]
2026-04-23 11:22 ` Tauro, Riana
2026-04-21 14:50 ` [PATCH v3 3/5] drm/xe/xe_ras: Add helper to clear error counter Riana Tauro
2026-04-23 11:01 ` Raag Jadav
2026-04-23 11:16 ` Tauro, Riana
2026-04-23 12:21 ` Raag Jadav
2026-04-21 14:51 ` [PATCH v3 4/5] drm/xe/xe_drm_ras: Wire get-counter support into xe_drm_ras for CRI Riana Tauro
2026-04-23 11:09 ` Raag Jadav
2026-04-23 11:18 ` Tauro, Riana
2026-04-21 14:51 ` [PATCH v3 5/5] drm/xe/ras: Add flag for Xe RAS Riana Tauro
2026-04-21 15:45 ` ✓ Xe.CI.BAT: success for Add get-error-counter and clear-error-counter support for CRI (rev2) Patchwork
2026-04-21 18:06 ` ✗ 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=aen5oJTmbeQuNi4_@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 \
--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