From: Andi Shyti <andi.shyti@linux.intel.com>
To: "Purkait, Soham" <soham.purkait@intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
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 2/2] drm/xe/xe_ras: Add RAS support for GPU health indicator
Date: Mon, 20 Apr 2026 19:35:10 +0200 [thread overview]
Message-ID: <aeZjzhyKjdh27lSP@ashyti-mobl2.lan> (raw)
In-Reply-To: <bd5d4112-36c1-4e9f-b06e-08213922c157@intel.com>
Hi Soham,
On Mon, Apr 20, 2026 at 09:49:32PM +0530, Purkait, Soham wrote:
> On 16-04-2026 17:24, Andi Shyti wrote:
> > On Thu, Apr 16, 2026 at 03:06:10PM +0530, Soham Purkait wrote:
> > > GPU health indicator exposes a single sysfs interface, gpu_health,
> > > at the device level, allowing administrators and management tools to
> > > query the GPU health status. The interface permits both read and write
> > > operations on PF and native functions, while on VFs it is exposed as
> > > read-only.
> > Can you describe better the interfaces? The input and output
> > values?
>
> Sure. I missed it in this series. I think it is better to be in cover-letter
> isn't it ?
I was referring to the commit log. Of course, you can also add
them in the cover letter, but that's up to you if you see it
necessary.
Andi
next prev parent reply other threads:[~2026-04-20 17:35 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
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 [this message]
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=aeZjzhyKjdh27lSP@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