From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
"Ruifeng.Wang@arm.com" <Ruifeng.Wang@arm.com>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH v3] config/arm: split march cfg into arch and features
Date: Tue, 20 Jul 2021 11:58:16 +0000 [thread overview]
Message-ID: <003505414cd647bfb5a984e45d773ed9@pantheon.tech> (raw)
In-Reply-To: <PH0PR18MB4086CCEE30F3322B1A0D57E2DEE29@PH0PR18MB4086.namprd18.prod.outlook.com>
> -----Original Message-----
> From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> Sent: Tuesday, July 20, 2021 9:25 AM
> To: Juraj Linkeš <juraj.linkes@pantheon.tech>; thomas@monjalon.net;
> david.marchand@redhat.com; bruce.richardson@intel.com;
> Honnappa.Nagarahalli@arm.com; Ruifeng.Wang@arm.com;
> fengchengwen@huawei.com; ferruh.yigit@intel.com; jerinjacobk@gmail.com;
> Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: dev@dpdk.org
> Subject: RE: [EXT] [dpdk-dev] [PATCH v3] config/arm: split march cfg into arch
> and features
>
> >Older compilers may not support all arch versions and all features that
> >the target SoC supports, in which case it's better to figure out the
> >highest arch version and features that the compiler supports.
> >Implement
> >a way to achieve this:
> >1. Find the highest arch version that the compiler supports, keeping in
> >mind the SoC arch version we're building. For example, if the SoC arch
> >version is arm8.2-a, but the compiler only supports arm8.1-a, use
> >arm8.1-a. On the other hand, if the compiler supports arm8.3-a (or
> >higher), use armv8.2-a.
> >2. With the architecture version locked, iterate over SoC features and
> >use all that are supported.
> >
> >In all cases, emit a warning if there's something unsupported by the
> >compiler.
> >
> >Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
>
>
> Should we add soc_features to allow individual SoCs to configure additional
> extensions they support?
> As we discussed previously [1] default Neoverse-n2 shouldn’t have crypto
> extension as it's an optional feature[2]. SoCs that are based on n2 can define it
> in soc_features.
>
>
> [1] http://patches.dpdk.org/project/dpdk/patch/20210505121423.850-1-
> pbhagavatula@marvell.com/
> [2] https://developer.arm.com/ip-products/processors/neoverse/neoverse-n2
Thanks for reminding me, there seemed to be an agreement between you and Honnappa about this, so I'll add it.
next prev parent reply other threads:[~2021-07-20 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 9:39 [dpdk-dev] [PATCH v1] " Juraj Linkeš
2021-06-29 9:39 ` [dpdk-dev] [PATCH v1] config/arm: split march cfg to " Juraj Linkeš
2021-07-06 8:21 ` [dpdk-dev] [PATCH v2] config/arm: split march cfg into " Juraj Linkeš
2021-07-12 13:02 ` [dpdk-dev] [PATCH v3] " Juraj Linkeš
2021-07-14 9:24 ` Ruifeng Wang
2021-07-16 3:42 ` fengchengwen
2021-07-16 12:22 ` Juraj Linkeš
2021-07-20 7:25 ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-07-20 11:58 ` Juraj Linkeš [this message]
2021-07-20 12:33 ` [dpdk-dev] [PATCH v3 1/2] " Juraj Linkeš
2021-07-20 12:33 ` [dpdk-dev] [PATCH v3 2/2] config/arm: make n2 'crypto' an optional feature Juraj Linkeš
2021-08-17 10:56 ` [dpdk-dev] [PATCH v4 1/2] config/arm: split march cfg into arch and features Juraj Linkeš
2021-08-17 10:56 ` [dpdk-dev] [PATCH v4 2/2] config/arm: make n2 'crypto' an optional feature Juraj Linkeš
2021-09-06 8:38 ` Ruifeng Wang
2021-08-17 10:59 ` [dpdk-dev] [PATCH v4 1/2] config/arm: split march cfg into arch and features Juraj Linkeš
2021-09-06 8:26 ` Ruifeng Wang
2021-09-16 16:17 ` 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=003505414cd647bfb5a984e45d773ed9@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=pbhagavatula@marvell.com \
--cc=thomas@monjalon.net \
/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).