From: Raag Jadav <raag.jadav@intel.com>
To: Soham Purkait <soham.purkait@intel.com>
Cc: intel-xe@lists.freedesktop.org, riana.tauro@intel.com,
anshuman.gupta@intel.com, aravind.iddamsetty@linux.intel.com,
badal.nilawar@intel.com, ravi.kishore.koppuravuri@intel.com,
mallesh.koujalagi@intel.com, andi.shyti@intel.com,
rodrigo.vivi@intel.com, anoop.c.vijay@intel.com
Subject: Re: [PATCH v9 1/1] drm/xe/xe_ras: Add RAS GPU health indicator
Date: Fri, 10 Jul 2026 06:36:05 +0200 [thread overview]
Message-ID: <alB2tbx64x7RRmWB@black.igk.intel.com> (raw)
In-Reply-To: <20260710041555.19974-4-soham.purkait@intel.com>
On Fri, Jul 10, 2026 at 09:45:57AM +0530, Soham Purkait wrote:
> Add a sysfs interface that reports the current GPU health state and
> lets admin users and management tools update it but is readable by all
> users. Requests are routed through the sysctrl mailbox. The interface
> is present only on platforms that support the GPU health indicator.
>
> The interface is a single read/write file at the device level:
>
> $ cat /sys/.../device/gpu_health
> ok
>
> $ echo critical > /sys/.../device/gpu_health
>
> $ cat /sys/.../device/gpu_health
> critical
...
> +++ b/drivers/gpu/drm/xe/xe_ras_types.h
> @@ -10,6 +10,21 @@
>
> #define XE_RAS_NUM_COUNTERS 16
>
> +/**
> + * enum xe_ras_health - gpu health values
> + *
> + * @XE_RAS_HEALTH_OK: gpu is healthy and operating normally.
> + * @XE_RAS_HEALTH_WARNING: gpu has minor issues but is still operational.
> + * @XE_RAS_HEALTH_CRITICAL: gpu is in a critical state and may not be operational.
> + * @XE_RAS_HEALTH_MAX: Sentinel value for validation
> + */
> +enum xe_ras_health {
> + XE_RAS_HEALTH_OK = 0,
> + XE_RAS_HEALTH_WARNING,
> + XE_RAS_HEALTH_CRITICAL,
> + XE_RAS_HEALTH_MAX
> +};
Shouldn't these be in the .c file (similar to severity and component)?
Raag
next prev parent reply other threads:[~2026-07-10 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 4:15 [PATCH v9 0/1] drm/xe: Add support for GPU health indicator Soham Purkait
2026-07-10 4:15 ` [PATCH v9 1/1] drm/xe/xe_ras: Add RAS " Soham Purkait
2026-07-10 4:36 ` Raag Jadav [this message]
2026-07-10 4:22 ` ✗ CI.checkpatch: warning for drm/xe: Add support for " Patchwork
2026-07-10 4:23 ` ✓ CI.KUnit: success " Patchwork
2026-07-10 5:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-10 14:04 ` ✓ Xe.CI.FULL: " 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=alB2tbx64x7RRmWB@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.