From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>, dev@dpdk.org
Cc: wathsala.vithanage@arm.com, nd@arm.com
Subject: Re: [RFC 2/2] config/arm: add NVIDIA Grace CPU
Date: Thu, 18 Jan 2024 11:10:35 +0800 [thread overview]
Message-ID: <82c88ffd-69c1-42c8-93a9-5a0f03a79c28@arm.com> (raw)
In-Reply-To: <20240118023204.2138662-2-honnappa.nagarahalli@arm.com>
On 2024/1/18 10:32 AM, Honnappa Nagarahalli wrote:
> Add meson build configuration for NVIDIA Grace platform
> with 64-bit Arm Neoverse V2 cores.
>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> ---
> config/arm/arm64_grace_linux_gcc | 16 ++++++++++++++++
> config/arm/meson.build | 10 ++++++++++
> 2 files changed, 26 insertions(+)
> create mode 100644 config/arm/arm64_grace_linux_gcc
>
> diff --git a/config/arm/arm64_grace_linux_gcc b/config/arm/arm64_grace_linux_gcc
> new file mode 100644
> index 0000000000..bde55b17a8
> --- /dev/null
> +++ b/config/arm/arm64_grace_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 = 'grace'
> diff --git a/config/arm/meson.build b/config/arm/meson.build
> index 18b595ead1..345a9dbf6b 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -424,6 +424,14 @@ soc_tys2500 = {
> 'numa': true
> }
>
> +soc_grace = {
> + 'description': 'NVIDIA Grace',
> + 'implementer': '0x41',
> + 'part_number': '0xd4f',
> + 'extra_march_features': ['crypto'],
> + 'numa': true
> +}
> +
> soc_graviton2 = {
> 'description': 'AWS Graviton2',
> 'implementer': '0x41',
> @@ -544,6 +552,7 @@ dpaa: NXP DPAA
> emag: Ampere eMAG
> ft2000plus: Phytium FT-2000+
> tys2500: Phytium TengYun S2500
> +grace: NVIDIA Grace
> graviton2: AWS Graviton2
> graviton3: AWS Graviton3
> hip10: HiSilicon HIP10
> @@ -575,6 +584,7 @@ socs = {
> 'emag': soc_emag,
> 'ft2000plus': soc_ft2000plus,
> 'tys2500': soc_tys2500,
> + 'grace': soc_grace,
> 'graviton2': soc_graviton2,
> 'graviton3': soc_graviton3,
> 'hip10': soc_hip10,
Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
next prev parent reply other threads:[~2024-01-18 3:10 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 [this message]
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=82c88ffd-69c1-42c8-93a9-5a0f03a79c28@arm.com \
--to=ruifeng.wang@arm.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--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).