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 v7 1/1] drm/xe/xe_ras: Add RAS GPU health indicator
Date: Wed, 8 Jul 2026 08:47:16 +0200 [thread overview]
Message-ID: <ak3ydOjMXBrOVKbC@black.igk.intel.com> (raw)
In-Reply-To: <20260708061221.4006706-4-soham.purkait@intel.com>
On Wed, Jul 08, 2026 at 11:42:23AM +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
...
> index 000000000000..9612b97b0f88
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-driver-intel-xe-ras
> @@ -0,0 +1,30 @@
> +What: /sys/bus/pci/drivers/xe/.../gpu_health
> +Date: April 2026
> +KernelVersion: 7.2
Unless there's time travel involved here that I'm not familiar with, we
should consider using correct[1] date and version.
[1] https://jnikula.github.io/linux-kernel-tea-leaves/
...
> +/**
> + * DOC: GPU Health Indicator
> + *
> + * On Intel Xe platforms that support the GPU health indicator interface,
> + * the driver exposes a sysfs attribute at the device level as:
> + *
> + * ``/sys/bus/pci/drivers/xe/<BDF>/gpu_health``
The attribute is already under device <BFD>, so I'm really unsure of "gpu"
is needed here. IMO it can simply be 'health' but I'll leave it to you all.
> + * Reading the attribute returns a single line containing the current GPU
> + * health state. Writing one of the valid values updates the same. Reads
> + * are available to all users; writes are restricted to administrative
> + * users only (attribute permissions ``0644``).
Why is it readable for all users? Is there such a requirement?
Raag
next prev parent reply other threads:[~2026-07-08 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 6:12 [PATCH v7 0/1] drm/xe: Add support for GPU health indicator Soham Purkait
2026-07-08 6:12 ` [PATCH v7 1/1] drm/xe/xe_ras: Add RAS " Soham Purkait
2026-07-08 6:47 ` Raag Jadav [this message]
2026-07-08 7:52 ` Purkait, Soham
2026-07-08 7:40 ` Tauro, Riana
2026-07-08 7:57 ` Purkait, Soham
2026-07-08 8:01 ` Tauro, Riana
2026-07-08 8:14 ` Purkait, Soham
2026-07-08 9:19 ` Tauro, Riana
2026-07-08 6:18 ` ✗ CI.checkpatch: warning for drm/xe: Add support for " Patchwork
2026-07-08 6:19 ` ✓ CI.KUnit: success " Patchwork
2026-07-08 6:54 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-08 8:11 ` ✓ 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=ak3ydOjMXBrOVKbC@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.