linux/tools/testing
Sean Christopherson 2680dcfb34 KVM: selftests: Set per-iteration variables at the start of each iteration
Set the per-iteration variables at the start of each iteration instead of
setting them before the loop, and at the end of each iteration.  To ensure
the vCPU doesn't race ahead before the first iteration, simply have the
vCPU worker want for sem_vcpu_cont, which conveniently avoids the need to
special case posting sem_vcpu_cont from the loop.

Link: https://lore.kernel.org/r/20250111003004.1235645-19-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
2025-02-12 09:00:56 -08:00
..
crypto/chacha20-s390
cxl cxl changes for v6.14 2025-01-29 11:23:22 -08:00
fault-injection
ktest ktest.pl: Fix typo "accesing" 2024-12-18 16:51:50 -05:00
kunit The various patchsets are summarized below. Plus of course many 2025-01-26 18:36:23 -08:00
memblock memblock: updates for 6.12-rc1 2024-09-25 11:35:19 -07:00
nvdimm Get rid of 'remove_new' relic from platform driver struct 2024-12-01 15:12:43 -08:00
radix-tree Xarray: do not return sibling entries from xas_find_marked() 2025-01-24 22:47:27 -08:00
scatterlist
selftests KVM: selftests: Set per-iteration variables at the start of each iteration 2025-02-12 09:00:56 -08:00
shared tools: fix atomic_set() definition to set the value correctly 2025-01-12 19:03:35 -08:00
vma tools: add VM_WARN_ON_VMG definition 2025-01-25 20:22:46 -08:00
vsock vsock/test: Add test for connect() retries 2025-01-29 18:50:37 -08:00