Something went wrong. Try again.
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Something went wrong. Try again.
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101This directory contains a mix of tests integrated with kselftest andstandalone stress tests.
kselftest tests===============
sve-probe-vls - Checks the SVE vector length enumeration interfacesve-ptrace - Checks the SVE ptrace interface
Running the non-kselftest tests===============================
sve-stress performs an SVE context switch stress test, as describedbelow.
(The fpsimd-stress test works the same way; just substitute "fpsimd" for"sve" in the following commands.)
The test runs until killed by the user.
If no context switch error was detected, you will see output such asthe following:
$ ./sve-stress(wait for some time)^CVector length: 512 bitsPID: 1573Terminated by signal 15, no error, iterations=9467, signals=1014Vector length: 512 bitsPID: 1575Terminated by signal 15, no error, iterations=9448, signals=1028Vector length: 512 bitsPID: 1577Terminated by signal 15, no error, iterations=9436, signals=1039Vector length: 512 bitsPID: 1579Terminated by signal 15, no error, iterations=9421, signals=1039Vector length: 512 bitsPID: 1581Terminated by signal 15, no error, iterations=9403, signals=1039Vector length: 512 bitsPID: 1583Terminated by signal 15, no error, iterations=9385, signals=1036Vector length: 512 bitsPID: 1585Terminated by signal 15, no error, iterations=9376, signals=1039Vector length: 512 bitsPID: 1587Terminated by signal 15, no error, iterations=9361, signals=1039Vector length: 512 bitsPID: 1589Terminated by signal 15, no error, iterations=9350, signals=1039
If an error was detected, details of the mismatch will be printedinstead of "no error".
Ideally, the test should be allowed to run for many minutes or hoursto maximise test coverage.
KVM stress testing==================
To try to reproduce the bugs that we have been observing, sve-stressshould be run in parallel in two KVM guests, while simultaneouslyrunning on the host.
1) Start 2 guests, using the following command for each:
$ lkvm run --console=virtio -pconsole=hvc0 --sve Image
(Depending on the hardware GIC implementation, you may also need--irqchip=gicv3. New kvmtool defaults to that if appropriate, but Ican't remember whether my branch is new enough for that. Try withoutthe option first.)
Kvmtool occupies the terminal until you kill it (Ctrl+A x),or until the guest terminates. It is therefore recommended to runeach instance in separate terminal (use screen or ssh etc.) Thisallows multiple guests to be run in parallel while running othercommands on the host.
Within the guest, the host filesystem is accessible, mounted on /host.
2) Run the sve-stress on *each* guest with the Vector-Length set to 32:guest$ ./vlset --inherit 32 ./sve-stress
3) Run the sve-stress on the host with the maximum Vector-Length:host$ ./vlset --inherit --max ./sve-stress
Again, the test should be allowed to run for many minutes or hours tomaximise test coverage.
If no error is detected, you will see output from each sve-stressinstance similar to that illustrated above; otherwise details of theobserved mismatches will be printed.