Running the mainline arm64 MTE selftests on a Pixel 8 exposed three independent reporting problems. Fix each issue independently, then add an arm64 Kconfig fragment covering the facilities used by the MTE tests.
Testing was performed on a Pixel 8 with an Android 6.1 kernel built with the new configuration. All nine static MTE binaries returned success. Changes since v1: - Add missing MTE TAP headers as an output-only cleanup and clarify why line buffering prevents duplicate GCR_EL1 plan output. - Validate KSM privileges and optional sysfs access before setup. - Move and expand the arm64 config fragment, and standardize subjects on the selftests/arm64 prefix. Muhammad Usama Anjum (5): selftests/arm64: Print TAP header selftests/arm64: Print missing MTE TAP headers selftests/arm64: Treat KSM merge_across_nodes as optional selftests/arm64: Fix MTE prctl TAP plan selftests/arm64: Add MTE test config fragment tools/testing/selftests/arm64/config | 17 ++++++++++ .../selftests/arm64/mte/check_buffer_fill.c | 2 ++ .../selftests/arm64/mte/check_child_memory.c | 2 ++ .../arm64/mte/check_gcr_el1_cswitch.c | 1 + .../arm64/mte/check_hugetlb_options.c | 2 ++ .../selftests/arm64/mte/check_ksm_options.c | 31 +++++++++++++++++-- .../selftests/arm64/mte/check_mmap_options.c | 2 ++ .../testing/selftests/arm64/mte/check_prctl.c | 2 +- .../arm64/mte/check_tags_inclusion.c | 2 ++ .../selftests/arm64/mte/check_user_mem.c | 2 ++ 10 files changed, 59 insertions(+), 4 deletions(-) create mode 100644 tools/testing/selftests/arm64/config -- 2.47.3
