From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Jerin Jacob <jerinj@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>, "nd@arm.com" <nd@arm.com>
Subject: RE: [EXT] Re: [PATCH 1/2] config/arm: fix CN10K minimum march requirement
Date: Fri, 19 Jan 2024 19:42:02 +0000 [thread overview]
Message-ID: <PH0PR18MB40863B31781DFB86A4CFD9B5DE702@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <7f0f7b5a-d2a2-4c02-afde-96c12c83daf8@arm.com>
> -----Original Message-----
> From: Ruifeng Wang <Ruifeng.Wang@arm.com>
> Sent: Thursday, January 18, 2024 7:32 AM
> To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Jerin Jacob
> <jerinj@marvell.com>; Bruce Richardson <bruce.richardson@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; nd@arm.com
> Subject: [EXT] Re: [PATCH 1/2] config/arm: fix CN10K minimum march
> requirement
>
> External Email
>
> ----------------------------------------------------------------------
>
> On 2024/1/4 5:18 PM, pbhagavatula@marvell.com wrote:
> > From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >
> > Meson selects march and mcpu based on compiler support and
> > partnumber, only the minimum required march should be defined
> > in cross compile configuration file.
> >
> > Fixes: 1b4c86a721c9 ("config/arm: add Marvell CN10K")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> > ---
> > config/arm/arm64_cn10k_linux_gcc | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/config/arm/arm64_cn10k_linux_gcc
> b/config/arm/arm64_cn10k_linux_gcc
> > index fa904af5d0..801a7ededd 100644
> > --- a/config/arm/arm64_cn10k_linux_gcc
> > +++ b/config/arm/arm64_cn10k_linux_gcc
> > @@ -10,7 +10,7 @@ cmake = 'cmake'
> > [host_machine]
> > system = 'linux'
> > cpu_family = 'aarch64'
> > -cpu = 'armv8.6-a'
> > +cpu = 'armv8-a'
> > endian = 'little'
> >
> > [properties]
>
> The host_machine.cpu in cross file doesn't take effect.
> There is an effort to remove the confusion. Can you have a review?
I tested the patchset with cross as cn10k and they look good, I will drop this patch.
Thanks,
Pavan.
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__patches.dpdk.org_project_dpdk_patch_20231205035259.3516625-2D3-
> 2Djoyce.kong-
> 40arm.com_&d=DwICaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=1cjuAHrGh745jH
> Nmj2fD85sUMIJ2IPIDsIJzo6FN6Z0&m=kvQolwCYorBpQ4nTOcW2ScJHHijEJtn
> QojGz8R6F6mWPl4nA-
> gIVpBLkzjAFCIpR&s=Huq9MHONkc50v4UTZtcmyIwY2tD3iFSMrZGuo_PvWSU
> &e=
prev parent reply other threads:[~2024-01-19 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 9:18 pbhagavatula
2024-01-18 2:02 ` Ruifeng Wang
2024-01-19 19:42 ` Pavan Nikhilesh Bhagavatula [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=PH0PR18MB40863B31781DFB86A4CFD9B5DE702@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
/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).