From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, david.marchand@redhat.com,
wathsala.vithanage@arm.com, dhruv.tripathi@arm.com, nd@arm.com,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [PATCH v2 2/4] config/arm: add generic V2 SoC
Date: Tue, 20 Feb 2024 01:45:31 +0000 [thread overview]
Message-ID: <20240220014533.1483934-2-honnappa.nagarahalli@arm.com> (raw)
In-Reply-To: <20240220014533.1483934-1-honnappa.nagarahalli@arm.com>
Add generic V2 CPU SoC. This will allow for compiling a binary
that will run on any SoC that uses V2 CPU.
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
---
config/arm/arm64_v2_linux_gcc | 16 ++++++++++++++++
config/arm/meson.build | 9 +++++++++
2 files changed, 25 insertions(+)
create mode 100644 config/arm/arm64_v2_linux_gcc
diff --git a/config/arm/arm64_v2_linux_gcc b/config/arm/arm64_v2_linux_gcc
new file mode 100644
index 0000000000..50d9be3da3
--- /dev/null
+++ b/config/arm/arm64_v2_linux_gcc
@@ -0,0 +1,16 @@
+[binaries]
+c = ['ccache', 'aarch64-linux-gnu-gcc']
+cpp = ['ccache', 'aarch64-linux-gnu-g++']
+ar = 'aarch64-linux-gnu-gcc-ar'
+strip = 'aarch64-linux-gnu-strip'
+pkgconfig = 'aarch64-linux-gnu-pkg-config'
+pcap-config = ''
+
+[host_machine]
+system = 'linux'
+cpu_family = 'aarch64'
+cpu = 'armv9-a'
+endian = 'little'
+
+[properties]
+platform = 'v2'
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 18b595ead1..f096ed9ebf 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -527,6 +527,13 @@ soc_bluefield3 = {
'numa': false
}
+soc_v2 = {
+ 'description': 'Arm Neoverse V2',
+ 'implementer': '0x41',
+ 'part_number': '0xd4f',
+ 'numa': true
+}
+
'''
Start of SoCs list
generic: Generic un-optimized build for armv8 aarch64 execution mode.
@@ -555,6 +562,7 @@ stingray: Broadcom Stingray
thunderx2: Marvell ThunderX2 T99
thunderxt88: Marvell ThunderX T88
thunderxt83: Marvell ThunderX T83
+v2: Arm Neoverse V2
End of SoCs list
'''
# The string above is included in the documentation, keep it in sync with the
@@ -586,6 +594,7 @@ socs = {
'thunderx2': soc_thunderx2,
'thunderxt88': soc_thunderxt88,
'thunderxt83': soc_thunderxt83,
+ 'v2': soc_v2,
}
dpdk_conf.set('RTE_ARCH_ARM', 1)
--
2.34.1
next prev parent reply other threads:[~2024-02-20 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 2:32 [RFC 1/2] config/arm: add Neoverse V2 part number Honnappa Nagarahalli
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 ` Honnappa Nagarahalli [this message]
2024-02-22 7:08 ` [PATCH v2 2/4] config/arm: add generic V2 SoC 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=20240220014533.1483934-2-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dhruv.tripathi@arm.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
--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).