From: Min Zhou <zhoumin@loongson.cn>
To: thomas@monjalon.net, david.marchand@redhat.com,
bruce.richardson@intel.com, anatoly.burakov@intel.com,
qiming.yang@intel.com, Yuying.Zhang@intel.com,
jgrajcia@cisco.com, konstantin.v.ananyev@yandex.ru,
zhoumin@loongson.cn
Cc: dev@dpdk.org, maobibo@loongson.cn
Subject: [PATCH v7 6/7] test/cpuflags: add test for LoongArch cpu flag
Date: Fri, 30 Sep 2022 16:02:27 +0800 [thread overview]
Message-ID: <20220930080228.864681-7-zhoumin@loongson.cn> (raw)
In-Reply-To: <20220930080228.864681-1-zhoumin@loongson.cn>
Add checks for all flag values defined in the LoongArch cpu
feature table.
Signed-off-by: Min Zhou <zhoumin@loongson.cn>
---
app/test/test_cpuflags.c | 41 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/app/test/test_cpuflags.c b/app/test/test_cpuflags.c
index 98a99c2c7d..a0e342ae48 100644
--- a/app/test/test_cpuflags.c
+++ b/app/test/test_cpuflags.c
@@ -281,6 +281,47 @@ test_cpuflags(void)
CHECK_FOR_FLAG(RTE_CPUFLAG_RISCV_ISA_Z);
#endif
+#if defined(RTE_ARCH_LOONGARCH)
+ printf("Check for CPUCFG:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_CPUCFG);
+
+ printf("Check for LAM:\t\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LAM);
+
+ printf("Check for UAL:\t\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_UAL);
+
+ printf("Check for FPU:\t\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_FPU);
+
+ printf("Check for LSX:\t\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LSX);
+
+ printf("Check for LASX:\t\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LASX);
+
+ printf("Check for CRC32:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_CRC32);
+
+ printf("Check for COMPLEX:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_COMPLEX);
+
+ printf("Check for CRYPTO:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_CRYPTO);
+
+ printf("Check for LVZ:\t\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LVZ);
+
+ printf("Check for LBT_X86:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LBT_X86);
+
+ printf("Check for LBT_ARM:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LBT_ARM);
+
+ printf("Check for LBT_MIPS:\t");
+ CHECK_FOR_FLAG(RTE_CPUFLAG_LBT_MIPS);
+#endif
+
/*
* Check if invalid data is handled properly
*/
--
2.31.1
next prev parent reply other threads:[~2022-09-30 8:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 8:02 [PATCH v7 0/7] Introduce support for LoongArch architecture Min Zhou
2022-09-30 8:02 ` [PATCH v7 1/7] eal/loongarch: support " Min Zhou
2022-10-03 17:15 ` David Marchand
2022-10-04 8:49 ` zhoumin
2022-09-30 8:02 ` [PATCH v7 2/7] net/ixgbe: add vector stubs for LoongArch Min Zhou
2022-09-30 8:02 ` [PATCH v7 3/7] net/memif: set memfd syscall ID on LoongArch Min Zhou
2022-09-30 8:02 ` [PATCH v7 4/7] net/tap: set BPF syscall ID for LoongArch Min Zhou
2022-09-30 8:02 ` [PATCH v7 5/7] examples/l3fwd: enable LoongArch operation Min Zhou
2022-09-30 8:02 ` Min Zhou [this message]
2022-09-30 8:02 ` [PATCH v7 7/7] ci: add LOONGARCH64 cross compilation job Min Zhou
2022-09-30 8:13 ` [PATCH v7 0/7] Introduce support for LoongArch architecture David Marchand
2022-09-30 10:05 ` zhoumin
2022-09-30 14:20 ` David Marchand
2022-10-01 14:25 ` zhoumin
2022-10-03 16:30 ` David Marchand
2022-10-04 8:49 ` zhoumin
2022-10-03 8:14 ` Ali Alnubani
2022-10-03 12:44 ` zhoumin
2022-10-04 6:59 ` David Marchand
2022-10-04 8:50 ` zhoumin
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=20220930080228.864681-7-zhoumin@loongson.cn \
--to=zhoumin@loongson.cn \
--cc=Yuying.Zhang@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=maobibo@loongson.cn \
--cc=qiming.yang@intel.com \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).