DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 07/12] app: test: added the new cpu flags of arm64 in test_cpuflags test case
Date: Tue, 3 Nov 2015 18:39:08 +0530	[thread overview]
Message-ID: <1446556153-18845-8-git-send-email-jerin.jacob@caviumnetworks.com> (raw)
In-Reply-To: <1446556153-18845-7-git-send-email-jerin.jacob@caviumnetworks.com>

Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
---
 app/test/test_cpuflags.c | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/app/test/test_cpuflags.c b/app/test/test_cpuflags.c
index 557458f..e8d0ce7 100644
--- a/app/test/test_cpuflags.c
+++ b/app/test/test_cpuflags.c
@@ -120,6 +120,32 @@ test_cpuflags(void)
 	CHECK_FOR_FLAG(RTE_CPUFLAG_NEON);
 #endif
 
+#if defined(RTE_ARCH_ARM64)
+	printf("Check for FP:\t\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_FP);
+
+	printf("Check for ASIMD:\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_NEON);
+
+	printf("Check for EVTSTRM:\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_EVTSTRM);
+
+	printf("Check for AES:\t\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_AES);
+
+	printf("Check for PMULL:\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_PMULL);
+
+	printf("Check for SHA1:\t\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_SHA1);
+
+	printf("Check for SHA2:\t\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_SHA2);
+
+	printf("Check for CRC32:\t");
+	CHECK_FOR_FLAG(RTE_CPUFLAG_CRC32);
+#endif
+
 #if defined(RTE_ARCH_X86_64) || defined(RTE_ARCH_I686)
 	printf("Check for SSE:\t\t");
 	CHECK_FOR_FLAG(RTE_CPUFLAG_SSE);
-- 
2.1.0

  reply	other threads:[~2015-11-03 13:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 13:09 [dpdk-dev] [PATCH 00/12] DPDK armv8-a support Jerin Jacob
2015-11-03 13:09 ` [dpdk-dev] [PATCH 01/12] eal: arm64: add armv8-a version of rte_atomic_64.h Jerin Jacob
2015-11-03 13:09   ` [dpdk-dev] [PATCH 02/12] eal: arm64: add armv8-a version of rte_cpuflags_64.h Jerin Jacob
2015-11-03 13:09     ` [dpdk-dev] [PATCH 03/12] eal: arm64: add armv8-a version of rte_prefetch_64.h Jerin Jacob
2015-11-03 13:09       ` [dpdk-dev] [PATCH 04/12] eal: arm64: add armv8-a version of rte_cycles_64.h Jerin Jacob
2015-11-03 13:09         ` [dpdk-dev] [PATCH 05/12] eal: arm64: rte_memcpy_64.h version based libc memcpy Jerin Jacob
2015-11-03 13:09           ` [dpdk-dev] [PATCH 06/12] eal: arm: ret_vector.h improvements Jerin Jacob
2015-11-03 13:09             ` Jerin Jacob [this message]
2015-11-03 13:09               ` [dpdk-dev] [PATCH 08/12] acl: arm64: acl implementation using NEON gcc intrinsic Jerin Jacob
2015-11-03 13:09                 ` [dpdk-dev] [PATCH 09/12] mk: add support for armv8 on top of armv7 Jerin Jacob
2015-11-03 13:09                   ` [dpdk-dev] [PATCH 10/12] mk: add support for thunderx machine target based armv8-a Jerin Jacob
2015-11-03 13:09                     ` [dpdk-dev] [PATCH 11/12] updated release note for armv8 support for DPDK 2.2 Jerin Jacob
2015-11-03 13:09                       ` [dpdk-dev] [PATCH 12/12] maintainers: claim responsibility for ARMv8 Jerin Jacob
2015-11-03 14:17 ` [dpdk-dev] [PATCH 00/12] DPDK armv8-a support Hunt, David
2015-11-03 16:38   ` Jerin Jacob
2015-11-05 14:39     ` Hunt, David

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=1446556153-18845-8-git-send-email-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    /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).