diff options
| author | Alex Williamson <alex.williamson@nvidia.com> | 2026-09-11 11:04:27 -0600 |
|---|---|---|
| committer | Alex Williamson <alex@shazbot.org> | 2026-09-25 06:11:39 -0600 |
| commit | e281aa76bc22865052dc7b7250403ff1258856a0 (patch) | |
| tree | 41a5315bbb2f19feb62c3f9c61b24f8b61c3f50a /tools/perf/scripts/python | |
| parent | 24acae9894b96624a69f07b708d58e591d11df98 (diff) | |
| download | linux-next-e281aa76bc22865052dc7b7250403ff1258856a0.tar.gz linux-next-e281aa76bc22865052dc7b7250403ff1258856a0.zip | |
vfio: selftests: Extend timeout for runner executions
When executed via the runner, ie. run_kselftest.sh, tests are subject
to a default 45s timeout. None of the igb, ioatdma, or nv_falcon
drivers can run the vfio_pci_driver_test within this window.
The igb driver is the worst due to the device getting wedged from bad
DMAs in mix_and_match and requiring the full transaction pending
delay prior to FLR.
This is even further exacerbated when the system implements
firmware-first error handling and the transaction pending scheduled
delays are preempted beyond expectations by SMIs.
Worst case observed runtime for the whole vfio_pci_driver_test on
such a setup is 450s. Round up to 600s.
Assisted-by: LLM
Reviewed-by: David Matlack <dmatlack@google.com>
Signed-off-by: Alex Williamson <alex.williamson@nvidia.com>
Link: https://lore.kernel.org/r/20260911170429.1642480-5-alex.williamson@nvidia.com
Signed-off-by: Alex Williamson <alex@shazbot.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions