From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "cburdick@nvidia.com" <cburdick@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>, nd <nd@arm.com>
Subject: RE: [PATCH] config: added support for NVIDIA ARM implementer ID
Date: Wed, 22 Feb 2023 09:59:11 +0000 [thread overview]
Message-ID: <AS8PR08MB7080CA67681CBCEE70EFD3DB9EAA9@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20230221173351.8439-1-cburdick@nvidia.com>
> -----Original Message-----
> From: cburdick@nvidia.com <cburdick@nvidia.com>
> Sent: Wednesday, February 22, 2023 1:34 AM
> To: Ruifeng Wang <Ruifeng.Wang@arm.com>
> Cc: dev@dpdk.org; Cliff Burdick <cburdick@nvidia.com>
> Subject: [PATCH] config: added support for NVIDIA ARM implementer ID
>
> From: Cliff Burdick <cburdick@nvidia.com>
>
> NVIDIA's Jetson Xavier is an ARM chip with NVIDIA as the implementer ID and a new part
> number. This patch adds support for this implementer ID and the part number.
>
> Signed-off-by: Cliff Burdick <cburdick@nvidia.com>
> ---
> .mailmap | 1 +
> config/arm/meson.build | 21 +++++++++++++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/.mailmap b/.mailmap
> index 6a91c11be4..2cb0d9e41b 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -230,6 +230,7 @@ Cian Ferriter <cian.ferriter@intel.com> Ciara Loftus
> <ciara.loftus@intel.com> Ciara Power <ciara.power@intel.com> Claire Murphy
> <claire.k.murphy@intel.com>
> +Cliff Burdick <cburdick@nvidia.com>
> Cody Doucette <doucette@bu.edu>
> Congwen Zhang <zhang.congwen@zte.com.cn> Conor Fogarty <conor.fogarty@intel.com> diff --
> git a/config/arm/meson.build b/config/arm/meson.build index 6442ec9596..6c3de22f16 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -159,6 +159,26 @@ implementer_cavium = {
> }
> }
>
> +implementer_nvidia = {
> + 'description': 'NVIDIA',
> + 'flags': [
> + ['RTE_CACHE_LINE_SIZE', 64]
> + ],
> + 'part_number_config': {
> + '0x4': {
> + 'march': 'armv8-a',
> + 'march_features': ['crc', 'crypto', 'lse'],
> + 'compiler_options': ['-march=armv8-a+crc+lse+simd'],
> + 'flags': [
> + ['RTE_USE_C11_MEM_MODEL', true],
> + ['RTE_MAX_LCORE', 8],
> + ['RTE_MAX_NUMA_NODES', 1],
> + ['RTE_MACHINE', '"armv8a"']
> + ]
> + }
> + }
> +}
> +
> implementer_ampere = {
> 'description': 'Ampere Computing',
> 'flags': [
> @@ -261,6 +281,7 @@ implementers = {
> '0x41': implementer_arm,
> '0x43': implementer_cavium,
> '0x48': implementer_hisilicon,
> + '0x4e': implementer_nvidia,
> '0x50': implementer_ampere,
> '0x51': implementer_qualcomm,
> '0x70': implementer_phytium,
> --
> 2.17.1
Only native build is supported with this change. To support cross build, soc section needs to be updated.
The below patch can be referenced:
http://patches.dpdk.org/project/dpdk/patch/20230220084827.3317796-3-rasland@nvidia.com/
next prev parent reply other threads:[~2023-02-22 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 17:33 cburdick
2023-02-22 9:59 ` Ruifeng Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 17:29 cburdick
2023-02-02 17:27 cburdick
2023-02-02 15:50 cburdick
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=AS8PR08MB7080CA67681CBCEE70EFD3DB9EAA9@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=cburdick@nvidia.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@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).