From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Riana Tauro <riana.tauro@intel.com>,
<igt-dev@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<kamil.konieczny@linux.intel.com>,
<aravind.iddamsetty@linux.intel.com>, <louis.chauvet@bootlin.com>
Subject: Re: [PATCH i-g-t 5/5] tests/intel/xe_configfs: Add test to validate survivability mode
Date: Tue, 22 Apr 2025 15:29:55 -0400 [thread overview]
Message-ID: <aAfuM25ln-ugZd_W@intel.com> (raw)
In-Reply-To: <rxwug7vusfk3npmlpvad43qhgo2rqa7jwi4wtfbhnei4f46sty@wjylvkykbjgr>
On Tue, Apr 22, 2025 at 08:57:35AM -0500, Lucas De Marchi wrote:
> On Tue, Apr 22, 2025 at 03:26:01PM +0530, Riana Tauro wrote:
> > The test validates if survivability mode is enabled on supported
> > platforms when configured using configfs attribute.
> >
> > Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> > ---
> > tests/intel/xe_configfs.c | 112 ++++++++++++++++++++++++++++++++++++++
> > tests/meson.build | 1 +
> > 2 files changed, 113 insertions(+)
> > create mode 100644 tests/intel/xe_configfs.c
> >
> > diff --git a/tests/intel/xe_configfs.c b/tests/intel/xe_configfs.c
> > new file mode 100644
> > index 000000000..414af4a86
> > --- /dev/null
> > +++ b/tests/intel/xe_configfs.c
>
>
> humn... does it make sense to test survivability mode in a xe_configfs
> test? configfs is just the way to trigger it. For completly different
> areas of the driver I don't think we should bundle the tests into a
> configfs test: we don't test if xe can be loaded without display in a
> xe_param.c test, or if we can inject faults in a xe_debugfs.c test, etc.
>
> My suggestion is to have a dedicated test for survivability in which
> configfs is part of it.
Well, that would work for survivability itself. But perhaps it is good
to have dedicated entry points for the knobs we expose, like we have
a single place to toggle all sysfs and debufs. So we don't forget to
add new cases and we have a single entry point to quickly exercises
the knobs.
>
> Lucas De Marchi
next prev parent reply other threads:[~2025-04-22 19:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 9:55 [PATCH i-g-t 0/5] Add test to validate survivability mode Riana Tauro
2025-04-22 9:55 ` [PATCH i-g-t 1/5] lib/igt_aux: Move is_mountpoint() to igt_aux Riana Tauro
2025-04-22 9:55 ` [PATCH i-g-t 2/5] lib/igt_configfs: Add helper to mount configfs Riana Tauro
2025-05-05 5:35 ` Aravind Iddamsetty
2025-05-07 11:05 ` José Expósito
2025-05-07 15:57 ` Kamil Konieczny
2025-04-22 9:55 ` [PATCH i-g-t 3/5] lib/igt_fs: Rename igt_io to igt_fs to add additional helpers Riana Tauro
2025-05-05 5:35 ` Aravind Iddamsetty
2025-05-07 11:08 ` José Expósito
2025-05-07 15:58 ` Kamil Konieczny
2025-04-22 9:56 ` [PATCH i-g-t 4/5] lib/igt_fs: Add helper functions to create and remove directories Riana Tauro
2025-05-05 5:35 ` Aravind Iddamsetty
2025-05-07 13:31 ` José Expósito
2025-05-07 15:48 ` Kamil Konieczny
2025-04-22 9:56 ` [PATCH i-g-t 5/5] tests/intel/xe_configfs: Add test to validate survivability mode Riana Tauro
2025-04-22 13:57 ` Lucas De Marchi
2025-04-22 19:29 ` Rodrigo Vivi [this message]
2025-04-24 4:17 ` Lucas De Marchi
2025-04-24 5:41 ` Riana Tauro
2025-05-12 10:54 ` Riana Tauro
2025-05-12 14:50 ` Lucas De Marchi
2025-04-24 13:00 ` Rodrigo Vivi
2025-05-05 7:08 ` Aravind Iddamsetty
2025-05-13 5:25 ` Riana Tauro
2025-04-22 19:51 ` ✓ i915.CI.BAT: success for Add test to validate survivability mode (rev2) Patchwork
2025-04-23 1:36 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-23 5:57 ` ✗ i915.CI.Full: " Patchwork
2025-04-23 21:59 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-24 9:51 ` ✗ 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=aAfuM25ln-ugZd_W@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=louis.chauvet@bootlin.com \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@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.