Mark Brown <broonie@xxxxxxxxxx> writes: > Verify that we can lock individual GCS mode bits, that other modes > aren't affected and as a side effect also that every combination of > modes can be enabled. > > Normally the inability to reenable GCS after disabling it would be an > issue with testing but fortunately the kselftest_harness runs each test > within a fork()ed child. This can be inconvenient for some kinds of > testing but here it means that each test is in a separate thread and > therefore won't be affected by other tests in the suite. > > Once we get toolchains with support for enabling GCS by default we will > need to take care to not do that in the build system but there are no > such toolchains yet so it is not yet an issue. > > Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@xxxxxxxxxx> > Signed-off-by: Mark Brown <broonie@xxxxxxxxxx> > --- > tools/testing/selftests/arm64/gcs/.gitignore | 1 + > tools/testing/selftests/arm64/gcs/Makefile | 2 +- > tools/testing/selftests/arm64/gcs/gcs-locking.c | 200 ++++++++++++++++++++++++ > 3 files changed, 202 insertions(+), 1 deletion(-) The gcs-locking test passes on my FVP setup: Tested-by: Thiago Jung Bauermann <thiago.bauermann@xxxxxxxxxx> -- Thiago
