On Fri, Sep 17, 2021 at 01:08:51PM +0100, Mark Brown wrote:
This series fixes up a few issues introduced into vec-syscfg during refactoring in the review process, then adds a new test which ensures that the behaviour when we attempt to set a vector length which is not supported by the current system matches what is documented in the SVE ABI documentation.
v2:
- Fix handling of missing VLs when checking that vector length setting works as expected.
With this series applied, I see a test failing under qemu with:
# selftests: arm64: vec-syscfg # TAP version 13 # 1..10 # ok 1 SVE default vector length 64 # ok 2 # SKIP Need to be root to write to /proc # ok 3 # SKIP Need to be root to write to /proc # ok 4 SVE current VL is 64 # ok 5 SVE set VL 64 and have VL 64 # ok 6 # SKIP SVE only one VL supported # ok 7 # SKIP SVE only one VL supported # ok 8 # SKIP SVE only one VL supported # ok 9 # SKIP SVE only one VL supported # # SVE VL 272 returned 256 not maximum 0 # # SVE VL 288 returned 256 not maximum 0 # # SVE VL 304 returned 256 not maximum 0 # # SVE VL 320 returned 256 not maximum 0 # # SVE VL 336 returned 256 not maximum 0 # # SVE VL 352 returned 256 not maximum 0
[repeat similar messages for ages]
# SVE VL 8160 returned 256 not maximum 0 # # SVE VL 8176 returned 256 not maximum 0 # # SVE VL 8192 returned 256 not maximum 0 # not ok 10 SVE prctl() set all VLs, 496 errors # # Totals: pass:3 fail:1 xfail:0 xpass:0 skip:6 error:0
Will