From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Mallesh Koujalagi <mallesh.koujalagi@intel.com>,
<intel-xe@lists.freedesktop.org>, <rodrigo.vivi@intel.com>,
<matthew.brost@intel.com>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<vinay.belgaumkar@intel.com>, <riana.tauro@intel.com>,
<karthik.poosa@intel.com>, <sk.anirban@intel.com>,
<raag.jadav@intel.com>, <aravind.iddamsetty@linux.intel.com>,
<umesh.nerlige.ramappa@intel.com>,
<dnyaneshwar.bhadane@intel.com>, <anoop.c.vijay@intel.com>
Subject: Re: [PATCH v5 7/7] drm/xe/sysctrl: Report 'System Controller event' error using SIGID
Date: Thu, 27 Aug 2026 13:06:18 +0200 [thread overview]
Message-ID: <1145b932-dd09-4307-b76e-0d4ff7008955@intel.com> (raw)
In-Reply-To: <20260825110542.1359776-16-mallesh.koujalagi@intel.com>
On 8/25/2026 1:05 PM, Mallesh Koujalagi wrote:
> Report 'System Controller event' error using xe_log() helpers.
>
> Signed-off-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
> ---
> v5:
> - Change Error as EXFULL. (Michal)
> - Update logging message.
> ---
> drivers/gpu/drm/xe/xe_sysctrl_event.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_sysctrl_event.c b/drivers/gpu/drm/xe/xe_sysctrl_event.c
> index da395148ee9d..7a3aa0aad6a3 100644
> --- a/drivers/gpu/drm/xe/xe_sysctrl_event.c
> +++ b/drivers/gpu/drm/xe/xe_sysctrl_event.c
> @@ -5,6 +5,7 @@
>
> #include "xe_device.h"
> #include "xe_irq.h"
> +#include "xe_log.h"
> #include "xe_printk.h"
> #include "xe_ras.h"
> #include "xe_sysctrl.h"
> @@ -25,23 +26,26 @@ static void get_pending_event(struct xe_sysctrl *sc, struct xe_sysctrl_mailbox_c
>
> ret = xe_sysctrl_send_command(sc, command, &len);
> if (ret) {
> - xe_err(xe, "sysctrl: failed to get pending event %d\n", ret);
> + xe_log_err(xe, SYSCTRL, ret, "Failed to get pending event\n");
> return;
> }
>
> if (len != sizeof(*response)) {
> - xe_err(xe, "sysctrl: unexpected event response length %zu (expected %zu)\n",
> - len, sizeof(*response));
> + xe_log_err(xe, SYSCTRL, -EMSGSIZE,
nit: maybe this should be -EPROTO (as it breaks ABI protocol)
> + "Unexpected event response length %zu (expected %zu)\n",
> + len, sizeof(*response));
> return;
> }
>
> if (response->event == XE_SYSCTRL_EVENT_THRESHOLD_CROSSED)
> xe_ras_counter_threshold_crossed(xe, response);
> else
> - xe_warn(xe, "sysctrl: unexpected event %#x\n", response->event);
> + xe_log_err_info(xe, SYSCTRL, -EPROTO,
and then this one should be -ENOPKG as maybe this is just our missing
implementation for some valid future event type?
> + "Unexpected event %#x\n", response->event);
>
> if (!--count) {
> - xe_err(xe, "sysctrl: event flooding\n");
> + xe_log_err(xe, SYSCTRL, -EXFULL,
> + "Ignored %u events due to flooding\n", response->count);
> return;
> }
>
anyway,
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
next prev parent reply other threads:[~2026-08-27 11:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 11:05 [PATCH v5 0/7] drm/xe/sysctrl: Clean up error handling in Mallesh Koujalagi
2026-08-25 11:05 ` [PATCH v5 1/7] drm/xe/sysctrl: Return error codes from sysctrl_wait_bit_clear() Mallesh Koujalagi
2026-08-25 11:24 ` sashiko-bot
2026-08-25 11:05 ` [PATCH v5 2/7] drm/xe/sysctrl: Return error codes from sysctrl_wait_bit_set() Mallesh Koujalagi
2026-08-25 11:24 ` sashiko-bot
2026-08-25 11:05 ` [PATCH v5 3/7] drm/xe/sysctrl: Make sysctrl_write_frame() void Mallesh Koujalagi
2026-08-25 11:05 ` [PATCH v5 4/7] drm/xe/sysctrl: Use xe_assert() for payload size validation Mallesh Koujalagi
2026-08-25 11:05 ` [PATCH v5 5/7] drm/xe/sysctrl: Improve firmware response error logging Mallesh Koujalagi
2026-08-25 11:22 ` sashiko-bot
2026-08-27 10:57 ` Michal Wajdeczko
2026-08-27 12:50 ` Mallesh, Koujalagi
2026-08-27 14:40 ` Michal Wajdeczko
2026-08-25 11:05 ` [PATCH v5 6/7] drm/xe/sysctrl: Log group and command ID on mailbox failure Mallesh Koujalagi
2026-08-25 11:21 ` sashiko-bot
2026-08-27 11:01 ` Michal Wajdeczko
2026-08-25 11:05 ` [PATCH v5 7/7] drm/xe/sysctrl: Report 'System Controller event' error using SIGID Mallesh Koujalagi
2026-08-25 11:18 ` sashiko-bot
2026-08-27 11:06 ` Michal Wajdeczko [this message]
2026-08-25 11:13 ` ✓ CI.KUnit: success for drm/xe/sysctrl: Clean up error handling in (rev2) Patchwork
2026-08-25 11:50 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-25 16:29 ` ✗ 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=1145b932-dd09-4307-b76e-0d4ff7008955@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=anoop.c.vijay@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=badal.nilawar@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.brost@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sk.anirban@intel.com \
--cc=umesh.nerlige.ramappa@intel.com \
--cc=vinay.belgaumkar@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