From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: dev@dpdk.org
Cc: wathsala.vithanage@arm.com, nd@arm.com,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [RFC 1/2] config/arm: add Neoverse V2 part number
Date: Thu, 18 Jan 2024 02:32:03 +0000 [thread overview]
Message-ID: <20240118023204.2138662-1-honnappa.nagarahalli@arm.com> (raw)
Add Arm Neoverse V2 part number
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
---
config/arm/meson.build | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 36f21d2259..18b595ead1 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -100,6 +100,16 @@ part_number_config_arm = {
['RTE_MAX_LCORE', 128],
['RTE_MAX_NUMA_NODES', 2]
]
+ },
+ '0xd4f': {
+ 'march_features': ['sve2'],
+ 'compiler_options': ['-mcpu=neoverse-v2'],
+ 'flags': [
+ ['RTE_MACHINE', '"neoverse-v2"'],
+ ['RTE_ARM_FEATURE_ATOMICS', true],
+ ['RTE_MAX_LCORE', 144],
+ ['RTE_MAX_NUMA_NODES', 2]
+ ]
}
}
implementer_arm = {
--
2.25.1
next reply other threads:[~2024-01-18 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 2:32 Honnappa Nagarahalli [this message]
2024-01-18 2:32 ` [RFC 2/2] config/arm: add NVIDIA Grace CPU Honnappa Nagarahalli
2024-01-18 3:10 ` Ruifeng Wang
2024-01-18 3:10 ` [RFC 1/2] config/arm: add Neoverse V2 part number Ruifeng Wang
2024-02-20 1:45 ` [PATCH v2 1/4] " Honnappa Nagarahalli
2024-02-20 1:45 ` [PATCH v2 2/4] config/arm: add generic V2 SoC Honnappa Nagarahalli
2024-02-22 7:08 ` Thomas Monjalon
2024-02-22 22:05 ` Honnappa Nagarahalli
2024-02-20 1:45 ` [PATCH v2 3/4] config/arm: add NVIDIA Grace CPU Honnappa Nagarahalli
2024-02-20 1:45 ` [PATCH v2 4/4] config/arm: add AWS Graviton4 CPU Honnappa Nagarahalli
2024-03-06 15:31 ` [PATCH v2 1/4] config/arm: add Neoverse V2 part number 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=20240118023204.2138662-1-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=wathsala.vithanage@arm.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 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).