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 v6 2/6] drm/xe/xe_ras: Add support to get error counter in CRI
Date: Mon, 18 May 2026 19:26:52 +0200 [thread overview]
Message-ID: <agtL3NF1BFyEX841@black.igk.intel.com> (raw)
In-Reply-To: <20260514052205.1340143-10-riana.tauro@intel.com>
On Thu, May 14, 2026 at 10:52:08AM +0530, Riana Tauro wrote:
> Add request/response structures and helper functions to query system
> controller to get error counter value.
...
> + xe_dbg(xe, "[RAS]: get counter value %u for %s %s\n", response.counter_value,
> + comp_to_str(response.counter.common.component),
> + sev_to_str(response.counter.common.severity));
A bit heavy handed with nesting :D
You can use a local counter which will also help remove the wrapping[1].
[1] https://lore.kernel.org/intel-xe/20260512191610.1817578-7-raag.jadav@intel.com/
...
> +/**
> + * struct xe_ras_get_counter_request - Request for get error counter
> + */
> +struct xe_ras_get_counter_request {
> + /** @counter: Error counter to be queried */
> + struct xe_ras_error_class counter;
> + /** @reserved: Reserved for future use */
> + u32 reserved;
> +} __packed;
> +
> +/**
> + * struct xe_ras_get_counter_response - Response for get error counter
> + */
> +struct xe_ras_get_counter_response {
> + /** @counter: Error counter that was queried */
> + struct xe_ras_error_class counter;
> + /** @counter_value: Current counter value */
> + u32 counter_value;
Nit: It's already 'get_counter', so perhaps just 'value'?
> + /** @timestamp: Timestamp when counter was last updated */
> + u64 timestamp;
> + /** @threshold_value: Threshold value for the counter */
> + u32 threshold_value;
Ditto, 'threshold'?
> + /** @counter_status: Status of the counter */
> + u32 counter_status:8;
'status'?
We should probably make these consistent across series', so let me know
which ones you prefer.
> + /** @reserved: Reserved for future use */
> + u32 reserved:24;
> + /** @reserved1: Reserved for future use */
> + u32 reserved1[56];
> +} __packed;
> +
> #endif
> diff --git a/drivers/gpu/drm/xe/xe_sysctrl_mailbox.c b/drivers/gpu/drm/xe/xe_sysctrl_mailbox.c
> index 3caa9f15875f..b7c4d8c37819 100644
> --- a/drivers/gpu/drm/xe/xe_sysctrl_mailbox.c
> +++ b/drivers/gpu/drm/xe/xe_sysctrl_mailbox.c
> @@ -293,6 +293,34 @@ static int sysctrl_send_command(struct xe_sysctrl *sc,
> return 0;
> }
>
> +/**
> + * xe_sysctrl_prepare_command() - Prepare System controller command structure
> + * @command: Sysctrl command structure
> + * @group: Command group ID
> + * @cmd_id: Command code
> + * @request: Pointer to request buffer (can be NULL)
> + * @request_len: Size of request buffer
> + * @response: Pointer to response buffer
> + * @response_len: Size of response buffer
> + *
> + * Helper function to prepare sysctrl command to be sent via xe_sysctrl_send_command()
> + */
> +void xe_sysctrl_prepare_command(struct xe_sysctrl_mailbox_command *command, u8 group, u8 cmd_id,
There's already a sysctrl_prepare_command() in place, so let's make this
a bit distinguishable.
PS: I've used xe_sysctrl_populate_command() in my series but I'll leave
it to you.
Raag
> + void *request, size_t request_len, void *response,
> + size_t response_len)
> +{
> + struct xe_sysctrl_app_msg_hdr header = {0};
> +
> + header.data = FIELD_PREP(APP_HDR_GROUP_ID_MASK, group) |
> + FIELD_PREP(APP_HDR_COMMAND_MASK, cmd_id);
> +
> + command->header = header;
> + command->data_in = request;
> + command->data_in_len = request_len;
> + command->data_out = response;
> + command->data_out_len = response_len;
> +}
next prev parent reply other threads:[~2026-05-18 17:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 5:22 [PATCH v6 0/6] Add get-error-counter and clear-error-counter support for CRI Riana Tauro
2026-05-14 4:55 ` ✗ CI.checkpatch: warning for Add get-error-counter and clear-error-counter support for CRI (rev5) Patchwork
2026-05-14 4:56 ` ✓ CI.KUnit: success " Patchwork
2026-05-14 5:22 ` [PATCH v6 1/6] drm/xe/uapi: Add additional error components to xe drm_ras Riana Tauro
2026-05-14 5:22 ` [PATCH v6 2/6] drm/xe/xe_ras: Add support to get error counter in CRI Riana Tauro
2026-05-18 17:26 ` Raag Jadav [this message]
2026-05-14 5:22 ` [PATCH v6 3/6] drm/xe/xe_ras: Add support to clear error counter Riana Tauro
2026-05-18 17:58 ` Raag Jadav
2026-05-14 5:22 ` [PATCH v6 4/6] drm/xe/xe_drm_ras: Wire get/clear counter callbacks Riana Tauro
2026-05-19 5:54 ` Raag Jadav
2026-05-14 5:22 ` [PATCH v6 5/6] drm/xe: Move xe drm_ras initialization Riana Tauro
2026-05-14 17:25 ` Raag Jadav
2026-05-14 5:22 ` [PATCH v6 6/6] drm/xe/xe_ras: Add drm_ras feature flag Riana Tauro
2026-05-14 5:43 ` ✓ Xe.CI.BAT: success for Add get-error-counter and clear-error-counter support for CRI (rev5) Patchwork
2026-05-15 1:10 ` ✗ 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=agtL3NF1BFyEX841@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