From: "Tauro, Riana" <riana.tauro@intel.com>
To: Raag Jadav <raag.jadav@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 v2 4/5] drm/xe/xe_ras: Add helper to clear error counter
Date: Mon, 20 Apr 2026 13:18:38 +0530 [thread overview]
Message-ID: <7f0babdb-a816-4ff2-830a-786476964d01@intel.com> (raw)
In-Reply-To: <ady2f_SEVmooxt7u@black.igk.intel.com>
On 4/13/2026 2:55 PM, Raag Jadav wrote:
> On Mon, Apr 06, 2026 at 08:24:43PM +0530, Riana Tauro wrote:
>> Add helper function to clear error counter value.
>>
>> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
>> ---
>> Note: This will be integrated with drm_ras implementation
>> once clear-error-counter patch is merged.
>> https://patchwork.freedesktop.org/series/163019/
>> ---
>> drivers/gpu/drm/xe/xe_ras.c | 48 +++++++++++++++++++++++++++++++++++++
>> drivers/gpu/drm/xe/xe_ras.h | 2 ++
>> 2 files changed, 50 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_ras.c b/drivers/gpu/drm/xe/xe_ras.c
>> index b5fdad2c801d..56abcb9783a4 100644
>> --- a/drivers/gpu/drm/xe/xe_ras.c
>> +++ b/drivers/gpu/drm/xe/xe_ras.c
>> @@ -121,3 +121,51 @@ int xe_ras_get_error_counter(struct xe_device *xe, const enum drm_xe_ras_error_s
>> guard(xe_pm_runtime)(xe);
>> return get_error_counter(xe, &error_class, value);
>> }
>> +
>> +/**
>> + * xe_ras_clear_error_counter() - Clear error counter value
>> + * @xe: xe device instance
>> + * @severity: Error severity level to be cleared
>> + * @error_id: Error component to be cleared
>> + *
>> + * This function clears 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_clear_error_counter(struct xe_device *xe, const enum drm_xe_ras_error_severity severity,
>> + u32 error_id)
>> +{
>> + struct xe_ras_clear_counter_response response = {0};
>> + struct xe_ras_clear_counter_request request = {0};
>> + struct xe_sysctrl_mailbox_command command = {0};
>> + struct xe_ras_error_class *error_class = &request.error_class;
>> + size_t rlen;
>> + int ret;
>> +
>> + error_class->common.severity = drm_to_xe_ras_severity[severity];
>> + error_class->common.component = drm_to_xe_ras_component[error_id];
>> +
>> + prepare_sysctrl_command(&command, XE_SYSCTRL_CMD_CLEAR_COUNTER, &request, sizeof(request),
>> + &response, sizeof(response));
> Nit: Probably worth having a set_error_counter(), we never know when might
> need it :D
I did think about this while working on the drm_ras command . Since this
is a error counter which is incremented for an error,
userspace shouldn't be allowed to set the count to anything other than
0. So retained the command as clear
Riana
>
> Raag
>
>> +
>> + guard(xe_pm_runtime)(xe);
>> + ret = xe_sysctrl_send_command(&xe->sc, &command, &rlen);
>> + if (ret) {
>> + xe_err(xe, "[RAS]: Sysctrl error ret %d\n", ret);
>> + return ret;
>> + }
>> +
>> + if (rlen != sizeof(response)) {
>> + xe_err(xe, "[RAS]: Sysctrl response size mismatch. Expected %zu, got %zu\n",
>> + sizeof(response), rlen);
>> + return -EINVAL;
>> + }
>> +
>> + if (response.status) {
>> + xe_err(xe, "[RAS]: Sysctrl Failed to clear counter %u\n", response.status);
>> + return -EIO;
>> + }
>> +
>> + return 0;
>> +}
>> diff --git a/drivers/gpu/drm/xe/xe_ras.h b/drivers/gpu/drm/xe/xe_ras.h
>> index e468c414148e..19e0e649d55f 100644
>> --- a/drivers/gpu/drm/xe/xe_ras.h
>> +++ b/drivers/gpu/drm/xe/xe_ras.h
>> @@ -12,5 +12,7 @@ struct xe_device;
>>
>> int xe_ras_get_error_counter(struct xe_device *xe, const enum drm_xe_ras_error_severity severity,
>> u32 error_id, u32 *value);
>> +int xe_ras_clear_error_counter(struct xe_device *xe, const enum drm_xe_ras_error_severity severity,
>> + u32 error_id);
>>
>> #endif
>> --
>> 2.47.1
>>
next prev parent reply other threads:[~2026-04-20 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 14:54 [PATCH v2 0/5] Add get-error-counter and clear-error-counter support for CRI Riana Tauro
2026-04-06 14:54 ` [PATCH v2 1/5] drm/xe/uapi: Add additional error components to XE drm_ras Riana Tauro
2026-04-06 14:54 ` [PATCH v2 2/5] drm/xe/xe_ras: Add structures and commands for get and clear counter Riana Tauro
2026-04-13 9:03 ` Raag Jadav
2026-04-20 7:50 ` Tauro, Riana
2026-04-06 14:54 ` [PATCH v2 3/5] drm/xe/xe_ras: Add support to query error counter for CRI Riana Tauro
2026-04-13 9:19 ` Raag Jadav
2026-04-20 6:33 ` Tauro, Riana
2026-04-20 8:21 ` Raag Jadav
2026-04-06 14:54 ` [PATCH v2 4/5] drm/xe/xe_ras: Add helper to clear error counter Riana Tauro
2026-04-13 9:25 ` Raag Jadav
2026-04-20 7:48 ` Tauro, Riana [this message]
2026-04-06 14:54 ` [PATCH v2 5/5] drm/xe/ras: Add flag for Xe RAS Riana Tauro
2026-04-06 14:54 ` ✗ CI.checkpatch: warning for Add get-error-counter and clear-error-counter support for CRI Patchwork
2026-04-06 14:56 ` ✓ CI.KUnit: success " Patchwork
2026-04-06 15:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-06 18:50 ` ✗ 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=7f0babdb-a816-4ff2-830a-786476964d01@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=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