1*e093256dSMark BrownThis directory contains a mix of tests integrated with kselftest and 2*e093256dSMark Brownstandalone stress tests. 3*e093256dSMark Brown 4*e093256dSMark Brownkselftest tests 5*e093256dSMark Brown=============== 6*e093256dSMark Brown 7*e093256dSMark Brownsve-probe-vls - Checks the SVE vector length enumeration interface 8*e093256dSMark Brownsve-ptrace - Checks the SVE ptrace interface 9*e093256dSMark Brown 10*e093256dSMark BrownRunning the non-kselftest tests 11*e093256dSMark Brown=============================== 12*e093256dSMark Brown 13*e093256dSMark Brownsve-stress performs an SVE context switch stress test, as described 14*e093256dSMark Brownbelow. 15*e093256dSMark Brown 16*e093256dSMark Brown(The fpsimd-stress test works the same way; just substitute "fpsimd" for 17*e093256dSMark Brown"sve" in the following commands.) 18*e093256dSMark Brown 19*e093256dSMark Brown 20*e093256dSMark BrownThe test runs until killed by the user. 21*e093256dSMark Brown 22*e093256dSMark BrownIf no context switch error was detected, you will see output such as 23*e093256dSMark Brownthe following: 24*e093256dSMark Brown 25*e093256dSMark Brown$ ./sve-stress 26*e093256dSMark Brown(wait for some time) 27*e093256dSMark Brown^C 28*e093256dSMark BrownVector length: 512 bits 29*e093256dSMark BrownPID: 1573 30*e093256dSMark BrownTerminated by signal 15, no error, iterations=9467, signals=1014 31*e093256dSMark BrownVector length: 512 bits 32*e093256dSMark BrownPID: 1575 33*e093256dSMark BrownTerminated by signal 15, no error, iterations=9448, signals=1028 34*e093256dSMark BrownVector length: 512 bits 35*e093256dSMark BrownPID: 1577 36*e093256dSMark BrownTerminated by signal 15, no error, iterations=9436, signals=1039 37*e093256dSMark BrownVector length: 512 bits 38*e093256dSMark BrownPID: 1579 39*e093256dSMark BrownTerminated by signal 15, no error, iterations=9421, signals=1039 40*e093256dSMark BrownVector length: 512 bits 41*e093256dSMark BrownPID: 1581 42*e093256dSMark BrownTerminated by signal 15, no error, iterations=9403, signals=1039 43*e093256dSMark BrownVector length: 512 bits 44*e093256dSMark BrownPID: 1583 45*e093256dSMark BrownTerminated by signal 15, no error, iterations=9385, signals=1036 46*e093256dSMark BrownVector length: 512 bits 47*e093256dSMark BrownPID: 1585 48*e093256dSMark BrownTerminated by signal 15, no error, iterations=9376, signals=1039 49*e093256dSMark BrownVector length: 512 bits 50*e093256dSMark BrownPID: 1587 51*e093256dSMark BrownTerminated by signal 15, no error, iterations=9361, signals=1039 52*e093256dSMark BrownVector length: 512 bits 53*e093256dSMark BrownPID: 1589 54*e093256dSMark BrownTerminated by signal 15, no error, iterations=9350, signals=1039 55*e093256dSMark Brown 56*e093256dSMark Brown 57*e093256dSMark BrownIf an error was detected, details of the mismatch will be printed 58*e093256dSMark Browninstead of "no error". 59*e093256dSMark Brown 60*e093256dSMark BrownIdeally, the test should be allowed to run for many minutes or hours 61*e093256dSMark Brownto maximise test coverage. 62*e093256dSMark Brown 63*e093256dSMark Brown 64*e093256dSMark BrownKVM stress testing 65*e093256dSMark Brown================== 66*e093256dSMark Brown 67*e093256dSMark BrownTo try to reproduce the bugs that we have been observing, sve-stress 68*e093256dSMark Brownshould be run in parallel in two KVM guests, while simultaneously 69*e093256dSMark Brownrunning on the host. 70*e093256dSMark Brown 71*e093256dSMark Brown1) Start 2 guests, using the following command for each: 72*e093256dSMark Brown 73*e093256dSMark Brown$ lkvm run --console=virtio -pconsole=hvc0 --sve Image 74*e093256dSMark Brown 75*e093256dSMark Brown(Depending on the hardware GIC implementation, you may also need 76*e093256dSMark Brown--irqchip=gicv3. New kvmtool defaults to that if appropriate, but I 77*e093256dSMark Browncan't remember whether my branch is new enough for that. Try without 78*e093256dSMark Brownthe option first.) 79*e093256dSMark Brown 80*e093256dSMark BrownKvmtool occupies the terminal until you kill it (Ctrl+A x), 81*e093256dSMark Brownor until the guest terminates. It is therefore recommended to run 82*e093256dSMark Browneach instance in separate terminal (use screen or ssh etc.) This 83*e093256dSMark Brownallows multiple guests to be run in parallel while running other 84*e093256dSMark Browncommands on the host. 85*e093256dSMark Brown 86*e093256dSMark BrownWithin the guest, the host filesystem is accessible, mounted on /host. 87*e093256dSMark Brown 88*e093256dSMark Brown2) Run the sve-stress on *each* guest with the Vector-Length set to 32: 89*e093256dSMark Brownguest$ ./vlset --inherit 32 ./sve-stress 90*e093256dSMark Brown 91*e093256dSMark Brown3) Run the sve-stress on the host with the maximum Vector-Length: 92*e093256dSMark Brownhost$ ./vlset --inherit --max ./sve-stress 93*e093256dSMark Brown 94*e093256dSMark Brown 95*e093256dSMark BrownAgain, the test should be allowed to run for many minutes or hours to 96*e093256dSMark Brownmaximise test coverage. 97*e093256dSMark Brown 98*e093256dSMark BrownIf no error is detected, you will see output from each sve-stress 99*e093256dSMark Browninstance similar to that illustrated above; otherwise details of the 100*e093256dSMark Brownobserved mismatches will be printed. 101