From: Zeng Heng <zengheng4@huawei.com> To: <will@kernel.org>, <catalin.marinas@arm.com>, <shuah@kernel.org>, <broonie@kernel.org> Cc: <zengheng4@huawei.com>, <xiexiuqi@huawei.com>, <linux-kselftest@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org> Subject: [PATCH -next v2 1/4] kselftest/arm64: add SHA1 and related features to hwcap test Date: Tue, 15 Aug 2023 12:09:12 +0800 [thread overview] Message-ID: <20230815040915.3966955-2-zengheng4@huawei.com> (raw) In-Reply-To: <20230815040915.3966955-1-zengheng4@huawei.com> Add the SHA1 and related features check in the set of hwcap tests. Signed-off-by: Zeng Heng <zengheng4@huawei.com> Reviewed-by: Mark Brown <broonie@kernel.org> --- tools/testing/selftests/arm64/abi/hwcap.c | 39 +++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c index af5490cae09b..c87a2e167ee8 100644 --- a/tools/testing/selftests/arm64/abi/hwcap.c +++ b/tools/testing/selftests/arm64/abi/hwcap.c @@ -87,6 +87,24 @@ static void rng_sigill(void) asm volatile("mrs x0, S3_3_C2_C4_0" : : : "x0"); } +static void sha1_sigill(void) +{ + /* SHA1H S0, S0 */ + asm volatile(".inst 0x5e280800" : : : ); +} + +static void sha2_sigill(void) +{ + /* SHA256H Q0, Q0, V0.4S */ + asm volatile(".inst 0x5e004000" : : : ); +} + +static void sha512_sigill(void) +{ + /* SHA512H Q0, Q0, V0.2D */ + asm volatile(".inst 0xce608000" : : : ); +} + static void sme_sigill(void) { /* RDSVL x0, #0 */ @@ -334,6 +352,27 @@ static const struct hwcap_data { .hwcap_bit = HWCAP2_RPRFM, .cpuinfo = "rprfm", }, + { + .name = "SHA1", + .at_hwcap = AT_HWCAP, + .hwcap_bit = HWCAP_SHA1, + .cpuinfo = "sha1", + .sigill_fn = sha1_sigill, + }, + { + .name = "SHA2", + .at_hwcap = AT_HWCAP, + .hwcap_bit = HWCAP_SHA2, + .cpuinfo = "sha2", + .sigill_fn = sha2_sigill, + }, + { + .name = "SHA512", + .at_hwcap = AT_HWCAP, + .hwcap_bit = HWCAP_SHA512, + .cpuinfo = "sha512", + .sigill_fn = sha512_sigill, + }, { .name = "SME", .at_hwcap = AT_HWCAP2, -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Zeng Heng <zengheng4@huawei.com> To: <will@kernel.org>, <catalin.marinas@arm.com>, <shuah@kernel.org>, <broonie@kernel.org> Cc: <zengheng4@huawei.com>, <xiexiuqi@huawei.com>, <linux-kselftest@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org> Subject: [PATCH -next v2 1/4] kselftest/arm64: add SHA1 and related features to hwcap test Date: Tue, 15 Aug 2023 12:09:12 +0800 [thread overview] Message-ID: <20230815040915.3966955-2-zengheng4@huawei.com> (raw) In-Reply-To: <20230815040915.3966955-1-zengheng4@huawei.com> Add the SHA1 and related features check in the set of hwcap tests. Signed-off-by: Zeng Heng <zengheng4@huawei.com> Reviewed-by: Mark Brown <broonie@kernel.org> --- tools/testing/selftests/arm64/abi/hwcap.c | 39 +++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c index af5490cae09b..c87a2e167ee8 100644 --- a/tools/testing/selftests/arm64/abi/hwcap.c +++ b/tools/testing/selftests/arm64/abi/hwcap.c @@ -87,6 +87,24 @@ static void rng_sigill(void) asm volatile("mrs x0, S3_3_C2_C4_0" : : : "x0"); } +static void sha1_sigill(void) +{ + /* SHA1H S0, S0 */ + asm volatile(".inst 0x5e280800" : : : ); +} + +static void sha2_sigill(void) +{ + /* SHA256H Q0, Q0, V0.4S */ + asm volatile(".inst 0x5e004000" : : : ); +} + +static void sha512_sigill(void) +{ + /* SHA512H Q0, Q0, V0.2D */ + asm volatile(".inst 0xce608000" : : : ); +} + static void sme_sigill(void) { /* RDSVL x0, #0 */ @@ -334,6 +352,27 @@ static const struct hwcap_data { .hwcap_bit = HWCAP2_RPRFM, .cpuinfo = "rprfm", }, + { + .name = "SHA1", + .at_hwcap = AT_HWCAP, + .hwcap_bit = HWCAP_SHA1, + .cpuinfo = "sha1", + .sigill_fn = sha1_sigill, + }, + { + .name = "SHA2", + .at_hwcap = AT_HWCAP, + .hwcap_bit = HWCAP_SHA2, + .cpuinfo = "sha2", + .sigill_fn = sha2_sigill, + }, + { + .name = "SHA512", + .at_hwcap = AT_HWCAP, + .hwcap_bit = HWCAP_SHA512, + .cpuinfo = "sha512", + .sigill_fn = sha512_sigill, + }, { .name = "SME", .at_hwcap = AT_HWCAP2, -- 2.25.1
next prev parent reply other threads:[~2023-08-15 4:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-15 4:09 [PATCH -next v2 0/4] kselftest/arm64: Add crypto-related feature checks to hwcap test Zeng Heng 2023-08-15 4:09 ` Zeng Heng 2023-08-15 4:09 ` Zeng Heng [this message] 2023-08-15 4:09 ` [PATCH -next v2 1/4] kselftest/arm64: add SHA1 and related features " Zeng Heng 2023-08-15 4:09 ` [PATCH -next v2 2/4] kselftest/arm64: add AES feature check " Zeng Heng 2023-08-15 4:09 ` Zeng Heng 2023-08-15 4:09 ` [PATCH -next v2 3/4] kselftest/arm64: add pmull feature " Zeng Heng 2023-08-15 4:09 ` Zeng Heng 2023-08-15 4:09 ` [PATCH -next v2 4/4] kselftest/arm64: add jscvt " Zeng Heng 2023-08-15 4:09 ` Zeng Heng 2023-08-16 18:25 ` [PATCH -next v2 0/4] kselftest/arm64: Add crypto-related feature checks " Will Deacon 2023-08-16 18:25 ` Will Deacon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230815040915.3966955-2-zengheng4@huawei.com \ --to=zengheng4@huawei.com \ --cc=broonie@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=shuah@kernel.org \ --cc=will@kernel.org \ --cc=xiexiuqi@huawei.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.