From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Feifei Wang <Feifei.Wang2@arm.com>, nd <nd@arm.com>,
nd <nd@arm.com>, nd <nd@arm.com>
Subject: RE: [EXT] [PATCH 1/2] config/arm: update config for Neoverse N2
Date: Thu, 8 Jun 2023 05:25:01 +0000 [thread overview]
Message-ID: <AS8PR08MB70803CB9B185A920F2838A999E50A@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB40860C07E165076738EB86BDDE50A@PH0PR18MB4086.namprd18.prod.outlook.com>
> -----Original Message-----
> From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> Sent: Thursday, June 8, 2023 12:35 PM
> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; bruce.richardson@intel.com
> Cc: dev@dpdk.org; jerinj@marvell.com; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>;
> Feifei Wang <Feifei.Wang2@arm.com>; nd <nd@arm.com>; nd <nd@arm.com>
> Subject: RE: [EXT] [PATCH 1/2] config/arm: update config for Neoverse N2
>
>
>
> > -----Original Message-----
> > From: Ruifeng Wang <Ruifeng.Wang@arm.com>
> > Sent: Thursday, June 8, 2023 9:59 AM
> > To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>;
> > bruce.richardson@intel.com
> > Cc: dev@dpdk.org; Jerin Jacob Kollanukkaran <jerinj@marvell.com>;
> > Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Feifei Wang
> > <Feifei.Wang2@arm.com>; nd <nd@arm.com>; nd <nd@arm.com>
> > Subject: RE: [EXT] [PATCH 1/2] config/arm: update config for Neoverse
> > N2
> >
> > > -----Original Message-----
> > > From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> > > Sent: Wednesday, June 7, 2023 11:12 PM
> > > To: Ruifeng Wang <Ruifeng.Wang@arm.com>; bruce.richardson@intel.com
> > > Cc: dev@dpdk.org; jerinj@marvell.com; Honnappa Nagarahalli
> > <Honnappa.Nagarahalli@arm.com>;
> > > Feifei Wang <Feifei.Wang2@arm.com>; nd <nd@arm.com>
> > > Subject: RE: [EXT] [PATCH 1/2] config/arm: update config for
> > > Neoverse N2
> > >
> > > > Updated maximum number of lcores and numa nodes to support
> > platforms
> > > > with multiple numa nodes.
> > > > Added mcpu compiler option.
> > > >
> > > > Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> > > > Reviewed-by: Feifei Wang <feifei.wang2@arm.com>
> > > > ---
> > > > config/arm/meson.build | 5 +++--
> > > > 1 file changed, 3 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/config/arm/meson.build b/config/arm/meson.build index
> > > > 5213434ca4..9e55e9f2a4 100644
> > > > --- a/config/arm/meson.build
> > > > +++ b/config/arm/meson.build
> > > > @@ -91,11 +91,12 @@ part_number_config_arm = {
> > > > '0xd49': {
> > > > 'march': 'armv8.5-a',
> > > > 'march_features': ['sve2'],
> > > > + 'compiler_options': ['-mcpu=neoverse-n2'],
> > >
> > > Hi Ruifeng,
> >
> > Hi Pavan,
> >
> > > I see the following warning when compiling with GCC 12
> > >
> > > cc1: warning: switch '-mcpu=neoverse-n2' conflicts with
> > > '-march=armv8.5-
> > a+sve2+crypto'
> > > switch
> > >
> > > Removing 'armv8.5-a' from the list makes the warning go away but
> > > what's
> > the correct march
> > > for neoverse-n2?
> > > Armv9.0-a is not a supported march flag in GCC.
> >
> > Thanks for pointing this out.
> > Neoverse-n2 is v9.0-a. The corresponding march flag in GCC is 'armv9-a' [1].
> > 'armv8.5-a' should be removed from the list. It was used when armv9-
> > a/neoverse-n2 is not available in compilers.
>
> I see, should I send a fix?
Sure. Please go ahead.
Thanks.
>
> >
> > [1] https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__gcc.gnu.org_onlinedocs_gcc-2D12.3.0_gcc_AArch64-
> > 2DOptions.html&d=DwIFAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=E3SgYMjtKCM
> > VsB-fmvgGV3o-
> > g_fjLhk5Pupi9ijohpc&m=v0RqCjWj9zEynw7pgt6ghZX4BNI5Vnk0UxA4sYAxRr
> > RtO8lLHUhKYCNTniy2Jb5L&s=tEj1y2WPKFeatDFYUFqX49tv-
> > 2rG2wx0UiWklOYUvhY&e=
> >
> > >
> > > > 'flags': [
> > > > ['RTE_MACHINE', '"neoverse-n2"'],
> > > > ['RTE_ARM_FEATURE_ATOMICS', true],
> > > > - ['RTE_MAX_LCORE', 64],
> > > > - ['RTE_MAX_NUMA_NODES', 1]
> > > > + ['RTE_MAX_LCORE', 128],
> > > > + ['RTE_MAX_NUMA_NODES', 2]
> > > > ]
> > > > }
> > > > }
> > > > --
> > > > 2.25.1
prev parent reply other threads:[~2023-06-08 5:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 5:57 Ruifeng Wang
2023-05-29 5:57 ` [PATCH 2/2] build: fix warning when running external command Ruifeng Wang
2023-05-29 8:12 ` Bruce Richardson
2023-05-29 7:41 ` [PATCH 1/2] config/arm: update config for Neoverse N2 Juraj Linkeš
2023-06-06 13:51 ` Thomas Monjalon
2023-06-07 15:11 ` [EXT] " Pavan Nikhilesh Bhagavatula
2023-06-08 4:29 ` Ruifeng Wang
2023-06-08 4:34 ` Pavan Nikhilesh Bhagavatula
2023-06-08 5:25 ` Ruifeng Wang [this message]
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=AS8PR08MB70803CB9B185A920F2838A999E50A@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Feifei.Wang2@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.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).