From: "Tauro, Riana" <riana.tauro@intel.com>
To: Karthik Poosa <karthik.poosa@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<raag.jadav@intel.com>, <jari.tahvanainen@intel.com>,
<sk.anirban@intel.com>, <kamil.konieczny@intel.com>,
<katarzyna.piecielska@intel.com>, <himanshu.girotra@intel.com>,
<ramadevi.gandi@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_survivability: Update category and mega feature
Date: Wed, 6 May 2026 12:31:30 +0530 [thread overview]
Message-ID: <1e8bbade-75fe-47a5-818b-2ffee745e61d@intel.com> (raw)
In-Reply-To: <20260422113403.843322-1-karthik.poosa@intel.com>
On 4/22/2026 5:04 PM, Karthik Poosa wrote:
> Update category and mega feature of xe_survivability same as xe_pmu for
> proper tracking in internal visualization tools.
Survivability is not really PMU. Why not use the same category as hwmon?
* Category: Core
* Mega feature: RAS
* Sub-category: RAS tests
* Functionality: Survivability mode
Thanks Riana
>
> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
> ---
> tests/intel/xe_survivability.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/intel/xe_survivability.c b/tests/intel/xe_survivability.c
> index e842a76ec..d5d7e048c 100644
> --- a/tests/intel/xe_survivability.c
> +++ b/tests/intel/xe_survivability.c
> @@ -23,8 +23,8 @@
>
> /**
> * TEST: Comprehensive survivability mode testing
> - * Category: Core
> - * Mega feature: General Core features
> + * Category: Metrics
> + * Mega feature: Performance Monitoring Unit
> * Sub-category: Telemetry
> * Functionality: survivability mode
> * Description: Validate survivability mode functionality
prev parent reply other threads:[~2026-05-06 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 11:34 [PATCH i-g-t] tests/intel/xe_survivability: Update category and mega feature Karthik Poosa
2026-04-22 15:11 ` ✓ i915.CI.BAT: success for " Patchwork
2026-04-22 15:28 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-23 1:19 ` ✗ i915.CI.Full: failure " Patchwork
2026-04-23 8:31 ` ✓ Xe.CI.FULL: success " Patchwork
2026-05-05 8:17 ` [PATCH i-g-t] " Tahvanainen, Jari
2026-05-06 7:01 ` Tauro, Riana [this message]
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=1e8bbade-75fe-47a5-818b-2ffee745e61d@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=himanshu.girotra@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=kamil.konieczny@intel.com \
--cc=karthik.poosa@intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=raag.jadav@intel.com \
--cc=ramadevi.gandi@intel.com \
--cc=sk.anirban@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