From: Mark Brown <broonie@kernel.org> Date: 2021-09-17 12:24:05
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.
Mark Brown (4):
selftests: arm64: Fix printf() format mismatch in vec-syscfg
selftests: arm64: Remove bogus error check on writing to files
selftests: arm64: Fix and enable test for setting current VL in
vec-syscfg
selftests: arm64: Verify that all possible vector lengths are handled
tools/testing/selftests/arm64/fp/vec-syscfg.c | 89 ++++++++++++++++---
1 file changed, 76 insertions(+), 13 deletions(-)
base-commit: 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Mark Brown <broonie@kernel.org> Date: 2021-09-17 12:25:01
The format for this error message calls for the plain text version of the
error but we weren't supply it.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/fp/vec-syscfg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -109,7 +109,7 @@ static int get_child_rdvl(struct vec_data *data)/* exec() a new binary which puts the VL on stdout */ret=execl(data->rdvl_binary,data->rdvl_binary,NULL);-fprintf(stderr,"execl(%s) failed: %d\n",+fprintf(stderr,"execl(%s) failed: %d (%s)\n",data->rdvl_binary,errno,strerror(errno));exit(EXIT_FAILURE);
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Mark Brown <broonie@kernel.org> Date: 2021-09-17 12:25:41
Due to some refactoring with the error handling we ended up mangling things
so we never actually set ret and therefore shouldn't be checking it.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/fp/vec-syscfg.c | 6 ------
1 file changed, 6 deletions(-)
@@ -180,7 +180,6 @@ static int file_read_integer(const char *name, int *val)staticintfile_write_integer(constchar*name,intval){FILE*f;-intret;f=fopen(name,"w");if(!f){
@@ -192,11 +191,6 @@ static int file_write_integer(const char *name, int val)fprintf(f,"%d",val);fclose(f);-if(ret<0){-ksft_test_result_fail("Error writing %d to %s\n",-val,name);-return-1;-}return0;}
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Mark Brown <broonie@kernel.org> Date: 2021-09-17 12:26:57
We had some test code for verifying that we can write the current VL via
the prctl() interface but the condition for the test was inverted which
wasn't noticed as it was never actually hooked up to the array of tests
we execute. Fix this.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/fp/vec-syscfg.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
@@ -329,12 +329,9 @@ static void prctl_set_same(struct vec_data *data)return;}-if(cur_vl!=data->rdvl())-ksft_test_result_pass("%s current VL is %d\n",-data->name,ret);-else-ksft_test_result_fail("%s prctl() VL %d but RDVL is %d\n",-data->name,ret,data->rdvl());+ksft_test_result(cur_vl==data->rdvl(),+"%s set VL %d and have VL %d\n",+data->name,cur_vl,data->rdvl());}/* Can we set a new VL for this process? */
From: Mark Brown <broonie@kernel.org> Date: 2021-09-17 12:27:41
As part of the enumeration interface for setting vector lengths it is valid
to set vector lengths not supported in the system, these will be rounded to
a supported vector length and returned from the prctl(). Add a test which
exercises this for every valid vector length and makes sure that the return
value is as expected and that this is reflected in the actual system state.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/fp/vec-syscfg.c | 71 +++++++++++++++++++
1 file changed, 71 insertions(+)
@@ -540,6 +540,76 @@ static void prctl_set_onexec(struct vec_data *data)file_write_integer(data->default_vl_file,data->default_vl);}+/* For each VQ verify that setting via prctl() does the right thing */+staticvoidprctl_set_all_vqs(structvec_data*data)+{+intret,vq,vl,new_vl;+interrors=0;++for(vq=SVE_VQ_MIN;vq<=SVE_VQ_MAX;vq++){+vl=sve_vl_from_vq(vq);++/* Attempt to set the VL */+ret=prctl(data->prctl_set,vl);+if(ret<0){+errors++;+ksft_print_msg("%s prctl set failed for %d: %d (%s)\n",+data->name,vl,+errno,strerror(errno));+continue;+}++new_vl=ret&PR_SVE_VL_LEN_MASK;++/* Check that we actually have the reported new VL */+if(data->rdvl()!=new_vl){+ksft_print_msg("Set %s VL %d but RDVL reports %d\n",+data->name,new_vl,data->rdvl());+errors++;+}++/* Was that the VL we asked for? */+if(new_vl==vl)+continue;++/* Should round up to the minimum VL if below it */+if(vl<data->min_vl){+if(new_vl!=data->min_vl){+ksft_print_msg("%s VL %d returned %d not minimum %d\n",+data->name,vl,new_vl,+data->min_vl);+errors++;+}++continue;+}++/* Should round down to maximum VL if above it */+if(vl>data->max_vl){+if(new_vl!=data->max_vl){+ksft_print_msg("%s VL %d returned %d not maximum %d\n",+data->name,vl,new_vl,+data->max_vl);+errors++;+}++continue;+}++/* Otherwise we should've rounded down */+if(!(new_vl<vl)){+ksft_print_msg("%s VL %d returned %d, did not round down\n",+data->name,vl,new_vl);+errors++;++continue;+}+}++ksft_test_result(errors==0,"%s prctl() set all VLs, %d errors\n",+data->name,errors);+}+typedefvoid(*test_type)(structvec_data*);staticconsttest_typetests[]={
Subject: [PATCH v2 4/4] selftests: arm64: Verify that all possible vector lengths
are handled
As part of the enumeration interface for setting vector lengths it is valid
to set vector lengths not supported in the system, these will be rounded to
a supported vector length and returned from the prctl(). Add a test which
exercises this for every valid vector length and makes sure that the return
value is as expected and that this is reflected in the actual system state.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/fp/vec-syscfg.c | 71
+++++++++++++++++++
1 file changed, 71 insertions(+)
@@ -540,6 +540,76 @@ static void prctl_set_onexec(struct vec_data *data)file_write_integer(data->default_vl_file,data->default_vl);}+/* For each VQ verify that setting via prctl() does the right thing */+staticvoidprctl_set_all_vqs(structvec_data*data)+{+intret,vq,vl,new_vl;+interrors=0;++for(vq=SVE_VQ_MIN;vq<=SVE_VQ_MAX;vq++){+vl=sve_vl_from_vq(vq);++/* Attempt to set the VL */+ret=prctl(data->prctl_set,vl);+if(ret<0){+errors++;+ksft_print_msg("%s prctl set failed for %d: %d
(%s)\n",
+ data->name, vl,
+ errno, strerror(errno));
+ continue;
+ }
+
+ new_vl = ret & PR_SVE_VL_LEN_MASK;
+
+ /* Check that we actually have the reported new VL */
+ if (data->rdvl() != new_vl) {
+ ksft_print_msg("Set %s VL %d but RDVL
reports %d\n",
+ data->name, new_vl, data->rdvl());
+ errors++;
+ }
+
+ /* Was that the VL we asked for? */
+ if (new_vl == vl)
+ continue;
+
+ /* Should round up to the minimum VL if below it */
+ if (vl < data->min_vl) {
+ if (new_vl != data->min_vl) {
+ ksft_print_msg("%s VL %d returned %d not
minimum %d\n",
+ data->name, vl, new_vl,
+ data->min_vl);
+ errors++;
+ }
+
+ continue;
+ }
+
+ /* Should round down to maximum VL if above it */
+ if (vl > data->max_vl) {
+ if (new_vl != data->max_vl) {
+ ksft_print_msg("%s VL %d returned %d not
maximum %d\n",
+ data->name, vl, new_vl,
+ data->max_vl);
+ errors++;
+ }
+
+ continue;
+ }
+
+ /* Otherwise we should've rounded down */
+ if (!(new_vl < vl)) {
+ ksft_print_msg("%s VL %d returned %d, did not round
down\n",
+ data->name, vl, new_vl);
+ errors++;
+
+ continue;
+ }
+ }
+
+ ksft_test_result(errors == 0, "%s prctl() set all VLs, %d errors\n",
+ data->name, errors);
+}
+
typedef void (*test_type)(struct vec_data *);
static const test_type tests[] = {
From: Will Deacon <will@kernel.org> Date: 2021-09-29 14:33:15
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Mark Brown <broonie@kernel.org> Date: 2021-09-29 14:46:10
On Wed, Sep 29, 2021 at 03:31:14PM +0100, Will Deacon wrote:
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
AFAICT this is due to running as a non-root user, the testsuite was
already having serious issues before then...
# 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
...as it's starting off by testing an interface that's only writable by
root and then relying on that information, the existing tests were also
not working usefully. qemu by default supports way more than one vector
length. In any case it's just the test added by the last patch that's
causing the output here, the first four patches should be fine and fix
issues.
I'm not sure it's a particularly good idea to run kselftest as a
non-root user TBH, it's going to cause you to skip a lot of tests.
From: Will Deacon <will@kernel.org> Date: 2021-09-29 15:37:12
On Wed, Sep 29, 2021 at 03:43:23PM +0100, Mark Brown wrote:
On Wed, Sep 29, 2021 at 03:31:14PM +0100, Will Deacon wrote:
quoted
With this series applied, I see a test failing under qemu with:
quoted
# 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
AFAICT this is due to running as a non-root user, the testsuite was
already having serious issues before then...
quoted
# 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
...as it's starting off by testing an interface that's only writable by
root and then relying on that information, the existing tests were also
not working usefully. qemu by default supports way more than one vector
length. In any case it's just the test added by the last patch that's
causing the output here, the first four patches should be fine and fix
issues.
I'm not sure it's a particularly good idea to run kselftest as a
non-root user TBH, it's going to cause you to skip a lot of tests.
Ah, thanks for pointing that out. It would probably be better to skip the
tests rather than fail them if they're not running with sufficient
permissions, but I'll go ahead and queue your v3 for now.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Mark Brown <broonie@kernel.org> Date: 2021-09-29 15:41:35
On Wed, Sep 29, 2021 at 04:35:12PM +0100, Will Deacon wrote:
On Wed, Sep 29, 2021 at 03:43:23PM +0100, Mark Brown wrote:
quoted
I'm not sure it's a particularly good idea to run kselftest as a
non-root user TBH, it's going to cause you to skip a lot of tests.
Ah, thanks for pointing that out. It would probably be better to skip the
tests rather than fail them if they're not running with sufficient
permissions, but I'll go ahead and queue your v3 for now.
Yes, that's what my v3 does - it skips the new test if it failed to
enumerate minimum and maximum vector lengths, like the other tests do.
On Wed, Sep 29, 2021 at 03:43:23PM +0100, Mark Brown wrote:
quoted
On Wed, Sep 29, 2021 at 03:31:14PM +0100, Will Deacon wrote:
quoted
With this series applied, I see a test failing under qemu with:
quoted
# 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
AFAICT this is due to running as a non-root user, the testsuite was
already having serious issues before then...
quoted
# 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
...as it's starting off by testing an interface that's only writable by
root and then relying on that information, the existing tests were also
not working usefully. qemu by default supports way more than one vector
length. In any case it's just the test added by the last patch that's
causing the output here, the first four patches should be fine and fix
issues.
I'm not sure it's a particularly good idea to run kselftest as a
non-root user TBH, it's going to cause you to skip a lot of tests.
We don't want Kselftest default run to be as root. Users can choose to
run as root which would be an explicit choice so they expect and plan
for the impact. Example panic test.
Ah, thanks for pointing that out. It would probably be better to skip the
tests rather than fail them if they're not running with sufficient
permissions, but I'll go ahead and queue your v3 for now.
Correct. I would like to see tests skipped not failed if either config
or permissions are lacking to run the tests.
thanks,
-- Shuah
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Mark Brown <broonie@kernel.org> Date: 2021-09-29 16:39:21
On Wed, Sep 29, 2021 at 10:26:49AM -0600, Shuah Khan wrote:
On 9/29/21 9:35 AM, Will Deacon wrote:
quoted
On Wed, Sep 29, 2021 at 03:43:23PM +0100, Mark Brown wrote:
quoted
quoted
I'm not sure it's a particularly good idea to run kselftest as a
non-root user TBH, it's going to cause you to skip a lot of tests.
We don't want Kselftest default run to be as root. Users can choose to
run as root which would be an explicit choice so they expect and plan
for the impact. Example panic test.
OTOH if you're trying to verify that the tests aren't broken it's not
that great since it'll mean that you'll not be exercising a bunch of the
code.
quoted
Ah, thanks for pointing that out. It would probably be better to skip the
tests rather than fail them if they're not running with sufficient
permissions, but I'll go ahead and queue your v3 for now.
Correct. I would like to see tests skipped not failed if either config
or permissions are lacking to run the tests.
As I said previously that's what my v3 that Will referenced above does.
On Wed, Sep 29, 2021 at 10:26:49AM -0600, Shuah Khan wrote:
quoted
On 9/29/21 9:35 AM, Will Deacon wrote:
quoted
On Wed, Sep 29, 2021 at 03:43:23PM +0100, Mark Brown wrote:
quoted
quoted
quoted
I'm not sure it's a particularly good idea to run kselftest as a
non-root user TBH, it's going to cause you to skip a lot of tests.
quoted
We don't want Kselftest default run to be as root. Users can choose to
run as root which would be an explicit choice so they expect and plan
for the impact. Example panic test.
OTOH if you're trying to verify that the tests aren't broken it's not
that great since it'll mean that you'll not be exercising a bunch of the
code.
Correct. Running Kselftest as root is the best approach for full coverage.
thanks,
-- Shuah
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel