From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jonathan.cavitt@intel.com,
Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
Adam Miszczak <adam.miszczak@linux.intel.com>,
Lukasz Laguna <lukasz.laguna@intel.com>,
Jakub Kolakowski <jakub1.kolakowski@intel.com>,
Michal Wajdeczko <Michal.Wajdeczko@intel.com>
Subject: [PATCH v2 i-g-t 2/2] tests/sriov_basic: Extract enable-vfs-bind-unbind-each-numvfs-all subtest
Date: Thu, 11 Jul 2024 15:58:58 +0200 [thread overview]
Message-ID: <20240711135858.975304-3-marcin.bernatowicz@linux.intel.com> (raw)
In-Reply-To: <20240711135858.975304-1-marcin.bernatowicz@linux.intel.com>
Extract the 'enable-vfs-bind-unbind-each-numvfs-all' subtest to
simplify blocklist management. Currently, there is no straightforward
method to block dynamic subsubtests, and running all of them becomes
too time-consuming.
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Michal Wajdeczko <Michal.Wajdeczko@intel.com>
Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
---
tests/sriov_basic.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/tests/sriov_basic.c b/tests/sriov_basic.c
index 95a462709..eff93ef7a 100644
--- a/tests/sriov_basic.c
+++ b/tests/sriov_basic.c
@@ -62,7 +62,13 @@ static void enable_vfs_autoprobe_on(int pf_fd, unsigned int num_vfs)
/**
* SUBTEST: enable-vfs-bind-unbind-each
* Description:
- * Verify VFs enabling with binding and unbinding the driver one be one to each of them
+ * Verify VFs enabling with binding and unbinding the driver one by one to each of them.
+ * Version includes dynamic subtests that allow specifying the number of enabled VFs as numvfs-N.
+ *
+ * SUBTEST: enable-vfs-bind-unbind-each-numvfs-all
+ * Description:
+ * Verify the enabling of all VFs and the sequential binding and unbinding of the driver
+ * to each one.
*/
static void enable_vfs_bind_unbind_each(int pf_fd, unsigned int num_vfs)
{
@@ -176,10 +182,12 @@ igt_main
enable_vfs_bind_unbind_each(pf_fd, num_vfs);
}
}
+ }
+
+ igt_describe("Verify the enabling of all VFs and the sequential binding and unbinding of the driver to each one");
+ igt_subtest("enable-vfs-bind-unbind-each-numvfs-all") {
for_max_sriov_num_vfs(pf_fd, num_vfs) {
- igt_dynamic_f("numvfs-all") {
- enable_vfs_bind_unbind_each(pf_fd, num_vfs);
- }
+ enable_vfs_bind_unbind_each(pf_fd, num_vfs);
}
}
--
2.31.1
next prev parent reply other threads:[~2024-07-11 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 13:58 [PATCH v2 i-g-t 0/2] Refactor sriov_basic test and blocklisting Marcin Bernatowicz
2024-07-11 13:58 ` [PATCH v2 i-g-t 1/2] tests/intel-ci/xe.blocklist: Blocklist SR-IOV stress tests Marcin Bernatowicz
2024-07-11 13:58 ` Marcin Bernatowicz [this message]
2024-07-11 14:01 ` [PATCH v2 i-g-t 0/2] Refactor sriov_basic test and blocklisting Cavitt, Jonathan
2024-07-11 15:04 ` ✗ Fi.CI.BUILD: failure for Refactor sriov_basic test and blocklisting (rev2) 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=20240711135858.975304-3-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=lukasz.laguna@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