From: Zeng Heng <zengheng4@huawei.com>
To: <kristina.martsenko@arm.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <broonie@kernel.org>, <shuah@kernel.org>
Cc: <linux-kselftest@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <xiexiuqi@huawei.com>,
<zengheng4@huawei.com>
Subject: [PATCH v2 2/5] kselftest/arm64: add crc32 feature to hwcap test
Date: Tue, 8 Aug 2023 21:40:33 +0800 [thread overview]
Message-ID: <20230808134036.668954-3-zengheng4@huawei.com> (raw)
In-Reply-To: <20230808134036.668954-1-zengheng4@huawei.com>
Add the CRC32 feature check in the set of hwcap tests.
Signed-off-by: Zeng Heng <zengheng4@huawei.com>
---
tools/testing/selftests/arm64/abi/hwcap.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c
index ec247587f2bf..70850bdb0e35 100644
--- a/tools/testing/selftests/arm64/abi/hwcap.c
+++ b/tools/testing/selftests/arm64/abi/hwcap.c
@@ -33,6 +33,11 @@
*/
typedef void (*sigill_fn)(void);
+static void crc32_sigill(void)
+{
+ asm volatile("crc32w w0, w0, w1");
+}
+
static void cssc_sigill(void)
{
/* CNT x0, x0 */
@@ -233,6 +238,13 @@ static const struct hwcap_data {
sigill_fn sigill_fn;
bool sigill_reliable;
} hwcaps[] = {
+ {
+ .name = "CRC32",
+ .at_hwcap = AT_HWCAP,
+ .hwcap_bit = HWCAP_CRC32,
+ .cpuinfo = "crc32",
+ .sigill_fn = crc32_sigill,
+ },
{
.name = "CSSC",
.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: <kristina.martsenko@arm.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <broonie@kernel.org>, <shuah@kernel.org>
Cc: <linux-kselftest@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <xiexiuqi@huawei.com>,
<zengheng4@huawei.com>
Subject: [PATCH v2 2/5] kselftest/arm64: add crc32 feature to hwcap test
Date: Tue, 8 Aug 2023 21:40:33 +0800 [thread overview]
Message-ID: <20230808134036.668954-3-zengheng4@huawei.com> (raw)
In-Reply-To: <20230808134036.668954-1-zengheng4@huawei.com>
Add the CRC32 feature check in the set of hwcap tests.
Signed-off-by: Zeng Heng <zengheng4@huawei.com>
---
tools/testing/selftests/arm64/abi/hwcap.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c
index ec247587f2bf..70850bdb0e35 100644
--- a/tools/testing/selftests/arm64/abi/hwcap.c
+++ b/tools/testing/selftests/arm64/abi/hwcap.c
@@ -33,6 +33,11 @@
*/
typedef void (*sigill_fn)(void);
+static void crc32_sigill(void)
+{
+ asm volatile("crc32w w0, w0, w1");
+}
+
static void cssc_sigill(void)
{
/* CNT x0, x0 */
@@ -233,6 +238,13 @@ static const struct hwcap_data {
sigill_fn sigill_fn;
bool sigill_reliable;
} hwcaps[] = {
+ {
+ .name = "CRC32",
+ .at_hwcap = AT_HWCAP,
+ .hwcap_bit = HWCAP_CRC32,
+ .cpuinfo = "crc32",
+ .sigill_fn = crc32_sigill,
+ },
{
.name = "CSSC",
.at_hwcap = AT_HWCAP2,
--
2.25.1
next prev parent reply other threads:[~2023-08-08 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 13:40 [PATCH v2 0/5] kselftest/arm64: add features check to hwcap test Zeng Heng
2023-08-08 13:40 ` Zeng Heng
2023-08-08 13:40 ` [PATCH v2 1/5] kselftest/arm64: add float-point feature " Zeng Heng
2023-08-08 13:40 ` Zeng Heng
2023-08-08 13:40 ` Zeng Heng [this message]
2023-08-08 13:40 ` [PATCH v2 2/5] kselftest/arm64: add crc32 " Zeng Heng
2023-08-08 13:40 ` [PATCH v2 3/5] kselftest/arm64: add DEF_SIGHANDLER_FUNC() and DEF_INST_RAISE_SIG() helpers Zeng Heng
2023-08-08 13:40 ` Zeng Heng
2023-08-08 13:40 ` [PATCH v2 4/5] kselftest/arm64: add test item that support to capturing the SIGBUS signal Zeng Heng
2023-08-08 13:40 ` Zeng Heng
2023-08-08 13:40 ` [PATCH v2 5/5] kselftest/arm64: add lse and lse2 features to hwcap test Zeng Heng
2023-08-08 13:40 ` Zeng Heng
2023-08-08 13:52 ` [PATCH v2 0/5] kselftest/arm64: add features check " Mark Brown
2023-08-08 13:52 ` Mark Brown
2023-08-11 11:44 ` Will Deacon
2023-08-11 11:44 ` 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=20230808134036.668954-3-zengheng4@huawei.com \
--to=zengheng4@huawei.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kristina.martsenko@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: link
Be 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.