From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Marcin Bernatowicz" <marcin.bernatowicz@linux.intel.com>,
"Adam Miszczak" <adam.miszczak@linux.intel.com>,
"Jakub Kolakowski" <jakub1.kolakowski@intel.com>,
"Lukasz Laguna" <lukasz.laguna@intel.com>,
"Michał Wajdeczko" <michal.wajdeczko@intel.com>,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Narasimha C V" <narasimha.c.v@intel.com>,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Satyanarayana K V P" <satyanarayana.k.v.p@intel.com>,
"Tomasz Lis" <tomasz.lis@intel.com>
Subject: [PATCH v4 i-g-t 0/2] tests/intel/xe_sriov_flr: Add parallel FLR subtest for SR-IOV VFs
Date: Wed, 5 Feb 2025 18:18:17 +0100 [thread overview]
Message-ID: <20250205171819.2485976-1-marcin.bernatowicz@linux.intel.com> (raw)
Introduce a new subtest flr-vfs-parallel to validate parallel FLR
execution on all VFs. This subtest ensures correct behavior during
simultaneous resets.
Introduce the flr-twice subtest, which initiates FLR twice in parallel
on the same VF. This subtest covers a use case where two FLRs can occur
within a short time frame, such as when starting a QEMU VM with
a passed VF.
v2: Reintroduce condition to reinitialize test data only if more VFs
remain to be tested (omitted when extracting execute_sequential_flr).
v3: Introduce threaded FLR initiation to achieve better parallelism
by mitigating 100ms reset delays.(Lukasz)
v4: Use total_flrs variable instead of repeating num_vfs * num_flrs_per_vf
(Lukasz)
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
Cc: Michał Winiarski <michal.winiarski@intel.com>
Cc: Narasimha C V <narasimha.c.v@intel.com>
Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: Tomasz Lis <tomasz.lis@intel.com>
Marcin Bernatowicz (2):
tests/intel/xe_sriov_flr: Add parallel FLR subtest for SR-IOV VFs
tests/intel/xe_sriov_flr: Add flr-twice subtest
tests/intel/xe_sriov_flr.c | 230 +++++++++++++++++++++++++++++++++----
1 file changed, 206 insertions(+), 24 deletions(-)
--
2.31.1
next reply other threads:[~2025-02-05 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 17:18 Marcin Bernatowicz [this message]
2025-02-05 17:18 ` [PATCH v4 i-g-t 1/2] tests/intel/xe_sriov_flr: Add parallel FLR subtest for SR-IOV VFs Marcin Bernatowicz
2025-02-05 17:18 ` [PATCH v4 i-g-t 2/2] tests/intel/xe_sriov_flr: Add flr-twice subtest Marcin Bernatowicz
2025-02-05 18:56 ` ✗ GitLab.Pipeline: warning for tests/intel/xe_sriov_flr: Add parallel FLR subtest for SR-IOV VFs (rev4) Patchwork
2025-02-05 19:13 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-05 21:16 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-06 9:58 ` Bernatowicz, Marcin
2025-02-06 12:10 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-06 12:21 ` ✓ i915.CI.BAT: " Patchwork
2025-02-06 12:59 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-06 17:27 ` ✗ i915.CI.Full: " 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=20250205171819.2485976-1-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=narasimha.c.v@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
--cc=tomasz.lis@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.