From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "mkashani@nvidia.com" <mkashani@nvidia.com>,
"rasland@nvidia.com" <rasland@nvidia.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: RE: [EXTERNAL] [PATCH] config/arm: fix meson for native instruction set Arm CPUs
Date: Wed, 19 Mar 2025 11:02:06 +0000 [thread overview]
Message-ID: <PH0PR18MB4086559122474B889285A20FDED92@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250319102505.596678-1-getelson@nvidia.com>
Hi Gregory,
> Arm meson.build unconditionally relays on the `extra_features`
> member of SoC configuration.
>
> SoC dictionary is populated for Arm CPUs with generic instruction set
> only.
> For Arm CPUs with native CPU instruction set the SoC dictionary is
> empty.
>
> meson setup failed for the BlueField-3 because it belongs to
> the native Arm CPU instruction set.
>
> The patch adds global definition for extra_features.
>
> Fixes: 7829776d0abf ("config/arm: add extra -march features")
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> ---
> config/arm/meson.build | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/config/arm/meson.build b/config/arm/meson.build
> index a97a28ebb7..f971ed3c1b 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -767,6 +767,7 @@ dpdk_conf.set('RTE_FORCE_INTRINSICS', 1)
>
> update_flags = false
> soc_flags = []
> +extra_features = []
We do set the default to be [] when extra_march_features is not found
In soc_config.
extra_features = soc_config.get('extra_march_features', [])
I have tested cross build[1] of bluefield3 with both meson 1.7.0 and 0.61.2
and didn’t see any failure which version of meson are you using?
[1]meson build --cross-file config/arm/arm64_bluefield3_linux_gcc
Thanks,
Pavan.
> if dpdk_conf.get('RTE_ARCH_32')
> # 32-bit build
> dpdk_conf.set('RTE_CACHE_LINE_SIZE', 64)
> --
> 2.45.2
next prev parent reply other threads:[~2025-03-19 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 10:25 Gregory Etelson
2025-03-19 11:02 ` Pavan Nikhilesh Bhagavatula [this message]
2025-03-19 11:10 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-03-19 11:48 ` 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=PH0PR18MB4086559122474B889285A20FDED92@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=jerinj@marvell.com \
--cc=mkashani@nvidia.com \
--cc=rasland@nvidia.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).