101 lines · plain
1This directory contains a mix of tests integrated with kselftest and2standalone stress tests.3 4kselftest tests5===============6 7sve-probe-vls - Checks the SVE vector length enumeration interface8sve-ptrace - Checks the SVE ptrace interface9 10Running the non-kselftest tests11===============================12 13sve-stress performs an SVE context switch stress test, as described14below.15 16(The fpsimd-stress test works the same way; just substitute "fpsimd" for17"sve" in the following commands.)18 19 20The test runs until killed by the user.21 22If no context switch error was detected, you will see output such as23the following:24 25$ ./sve-stress26(wait for some time)27^C28Vector length: 512 bits29PID: 157330Terminated by signal 15, no error, iterations=9467, signals=101431Vector length: 512 bits32PID: 157533Terminated by signal 15, no error, iterations=9448, signals=102834Vector length: 512 bits35PID: 157736Terminated by signal 15, no error, iterations=9436, signals=103937Vector length: 512 bits38PID: 157939Terminated by signal 15, no error, iterations=9421, signals=103940Vector length: 512 bits41PID: 158142Terminated by signal 15, no error, iterations=9403, signals=103943Vector length: 512 bits44PID: 158345Terminated by signal 15, no error, iterations=9385, signals=103646Vector length: 512 bits47PID: 158548Terminated by signal 15, no error, iterations=9376, signals=103949Vector length: 512 bits50PID: 158751Terminated by signal 15, no error, iterations=9361, signals=103952Vector length: 512 bits53PID: 158954Terminated by signal 15, no error, iterations=9350, signals=103955 56 57If an error was detected, details of the mismatch will be printed58instead of "no error".59 60Ideally, the test should be allowed to run for many minutes or hours61to maximise test coverage.62 63 64KVM stress testing65==================66 67To try to reproduce the bugs that we have been observing, sve-stress68should be run in parallel in two KVM guests, while simultaneously69running on the host.70 711) Start 2 guests, using the following command for each:72 73$ lkvm run --console=virtio -pconsole=hvc0 --sve Image74 75(Depending on the hardware GIC implementation, you may also need76--irqchip=gicv3. New kvmtool defaults to that if appropriate, but I77can't remember whether my branch is new enough for that. Try without78the option first.)79 80Kvmtool occupies the terminal until you kill it (Ctrl+A x),81or until the guest terminates. It is therefore recommended to run82each instance in separate terminal (use screen or ssh etc.) This83allows multiple guests to be run in parallel while running other84commands on the host.85 86Within the guest, the host filesystem is accessible, mounted on /host.87 882) Run the sve-stress on *each* guest with the Vector-Length set to 32:89guest$ ./vlset --inherit 32 ./sve-stress90 913) Run the sve-stress on the host with the maximum Vector-Length:92host$ ./vlset --inherit --max ./sve-stress93 94 95Again, the test should be allowed to run for many minutes or hours to96maximise test coverage.97 98If no error is detected, you will see output from each sve-stress99instance similar to that illustrated above; otherwise details of the100observed mismatches will be printed.101