Now that a process can control its DEXCR to some extent, make the
hashchk tests more reliable by explicitly setting the local and onexec
NPHIE aspect.

Signed-off-by: Benjamin Gray <bg...@linux.ibm.com>
---
 tools/testing/selftests/powerpc/dexcr/hashchk_test.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/tools/testing/selftests/powerpc/dexcr/hashchk_test.c 
b/tools/testing/selftests/powerpc/dexcr/hashchk_test.c
index 7d5658c9ebe4..645224bdc142 100644
--- a/tools/testing/selftests/powerpc/dexcr/hashchk_test.c
+++ b/tools/testing/selftests/powerpc/dexcr/hashchk_test.c
@@ -21,8 +21,14 @@
 static int require_nphie(void)
 {
        SKIP_IF_MSG(!dexcr_exists(), "DEXCR not supported");
+
+       pr_set_dexcr(PR_PPC_DEXCR_NPHIE, PR_PPC_DEXCR_CTRL_SET | 
PR_PPC_DEXCR_CTRL_SET_ONEXEC);
+
+       if (get_dexcr(EFFECTIVE) & DEXCR_PR_NPHIE)
+               return 0;
+
        SKIP_IF_MSG(!(get_dexcr(EFFECTIVE) & DEXCR_PR_NPHIE),
-                   "DEXCR[NPHIE] not enabled");
+                   "Failed to enable DEXCR[NPHIE]");
 
        return 0;
 }
-- 
2.44.0

Reply via email to