public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.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, raag.jadav@intel.com,
	ravi.kishore.koppuravuri@intel.com, mallesh.koujalagi@intel.com,
	anoop.c.vijay@intel.com
Subject: Re: [PATCH v1 1/2] drm/xe/xe_ras: Add structures and commands for RAS GPU health indicator
Date: Thu, 16 Apr 2026 13:39:16 +0200	[thread overview]
Message-ID: <aeDKZGVmVextYczY@ashyti-mobl2.lan> (raw)
In-Reply-To: <20260416093610.4085667-2-soham.purkait@intel.com>

Hi Soham,

On Thu, Apr 16, 2026 at 03:06:09PM +0530, Soham Purkait wrote:
> Add the sysctrl commands and response structures for GPU health
> indicator supported by RAS.

Can you please describe better the structures you are adding?

> Signed-off-by: Soham Purkait <soham.purkait@intel.com>

...

> +/**
> + * typedef xe_ras_health_status_t - Device health status values (8-bit)
> + *
> + * Three-state health indicator value reported by system controller commands.
> + *
> + * The expected values are:
> + * - 0: ok  - The device is healthy and operating within normal parameters.
> + * - 1: warning  - The device is experiencing minor issues but is still operational.
> + * - 2: critical  - The device is in a critical state and may not be operational.
> + */
> +typedef u8 xe_ras_health_status_t;

Please, don't add another definition of u8. Keep it u8. If you
expect only those three values (or at least a limited number of
values), you can define an enum.

Andi

  reply	other threads:[~2026-04-16 11:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16  9:36 [PATCH v1 0/2] drm/xe: Add support for GPU health indicator Soham Purkait
2026-04-16  9:36 ` [PATCH v1 1/2] drm/xe/xe_ras: Add structures and commands for RAS " Soham Purkait
2026-04-16 11:39   ` Andi Shyti [this message]
2026-04-17 14:45   ` Rodrigo Vivi
2026-04-16  9:36 ` [PATCH v1 2/2] drm/xe/xe_ras: Add RAS support for " Soham Purkait
2026-04-16 11:54   ` Andi Shyti
2026-04-17 14:51     ` Rodrigo Vivi
2026-04-20 15:26       ` Andi Shyti
2026-04-20 19:51         ` Rodrigo Vivi
2026-04-21 12:56           ` Andi Shyti
2026-04-21 13:21             ` Rodrigo Vivi
2026-04-22  6:05           ` Purkait, Soham
2026-04-20 16:19     ` Purkait, Soham
2026-04-20 17:35       ` Andi Shyti
2026-04-16  9:55 ` ✗ CI.checkpatch: warning for drm/xe: Add " Patchwork
2026-04-16  9:56 ` ✓ CI.KUnit: success " Patchwork
2026-04-16 10:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-16 12:01 ` ✗ 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=aeDKZGVmVextYczY@ashyti-mobl2.lan \
    --to=andi.shyti@linux.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=raag.jadav@intel.com \
    --cc=ravi.kishore.koppuravuri@intel.com \
    --cc=riana.tauro@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