DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
	bruce.richardson@intel.com, Honnappa.Nagarahalli@arm.com,
	Ruifeng.Wang@arm.com, fengchengwen@huawei.com,
	ferruh.yigit@intel.com, jerinjacobk@gmail.com,
	jerinj@marvell.com, pbhagavatula@marvell.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [dpdk-dev] [PATCH v4 2/2] config/arm: make n2 'crypto' an optional feature
Date: Tue, 17 Aug 2021 12:56:50 +0200	[thread overview]
Message-ID: <1629197810-26453-2-git-send-email-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <1629197810-26453-1-git-send-email-juraj.linkes@pantheon.tech>

Not all Neoverse-N2 cpus must support the crypto feature/extension which
makes it an optional feature. Only enable the feature for SoCs which
support it.

Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
---
v4: rebase
---
 config/arm/meson.build | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index c11efa1583..c9bcd089df 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -76,7 +76,7 @@ part_number_config_arm = {
     },
     '0xd49': {
         'march': 'armv8.5-a',
-        'march_features': ['crypto', 'sve2'],
+        'march_features': ['sve2'],
         'flags': [
             ['RTE_MACHINE', '"neoverse-n2"'],
             ['RTE_ARM_FEATURE_ATOMICS', true],
@@ -278,6 +278,7 @@ soc_cn10k = {
         ['RTE_MAX_NUMA_NODES', 1]
     ],
     'part_number': '0xd49',
+    'extra_march_features': ['crypto'],
     'numa': false
 }
 
-- 
2.20.1


  reply	other threads:[~2021-08-17 10:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  9:39 [dpdk-dev] [PATCH v1] config/arm: split march cfg into arch and features Juraj Linkeš
2021-06-29  9:39 ` [dpdk-dev] [PATCH v1] config/arm: split march cfg to " Juraj Linkeš
2021-07-06  8:21 ` [dpdk-dev] [PATCH v2] config/arm: split march cfg into " Juraj Linkeš
2021-07-12 13:02   ` [dpdk-dev] [PATCH v3] " Juraj Linkeš
2021-07-14  9:24     ` Ruifeng Wang
2021-07-16  3:42       ` fengchengwen
2021-07-16 12:22         ` Juraj Linkeš
2021-07-20  7:25     ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-07-20 11:58       ` Juraj Linkeš
2021-07-20 12:33     ` [dpdk-dev] [PATCH v3 1/2] " Juraj Linkeš
2021-07-20 12:33       ` [dpdk-dev] [PATCH v3 2/2] config/arm: make n2 'crypto' an optional feature Juraj Linkeš
2021-08-17 10:56       ` [dpdk-dev] [PATCH v4 1/2] config/arm: split march cfg into arch and features Juraj Linkeš
2021-08-17 10:56         ` Juraj Linkeš [this message]
2021-09-06  8:38           ` [dpdk-dev] [PATCH v4 2/2] config/arm: make n2 'crypto' an optional feature Ruifeng Wang
2021-08-17 10:59         ` [dpdk-dev] [PATCH v4 1/2] config/arm: split march cfg into arch and features Juraj Linkeš
2021-09-06  8:26         ` Ruifeng Wang
2021-09-16 16:17         ` Thomas Monjalon

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=1629197810-26453-2-git-send-email-juraj.linkes@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=pbhagavatula@marvell.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).