From: Luca Boccassi <bluca@debian.org>
To: Vimal Chungath <vcchunga@amazon.com>
Cc: Honnappa.Nagarahalli@arm.com, alisaidi@amazon.com,
bruce.richardson@intel.com, stable@dpdk.org,
thomas@monjalon.net
Subject: Re: [dpdk-stable] [19.11] [PATCH 1/1] config: add Graviton2(arm64) defconfig
Date: Wed, 07 Oct 2020 10:18:16 +0100 [thread overview]
Message-ID: <c2bf394e7e38bde86d66d6c34387de12a1ae6da0.camel@debian.org> (raw)
In-Reply-To: <20201006184455.31566-1-vcchunga@amazon.com>
On Tue, 2020-10-06 at 11:44 -0700, Vimal Chungath wrote:
> On 10/6/20 1:12 AM, Luca Boccassi wrote:
> >
> > On Mon, 2020-10-05 at 11:50 -0700, Vimal Chungath wrote:
> > > This patch adds make build configuration for AWS Graviton2 platform
> > > based on ARM Neoverse N1. Meson build works but uses configuration for
> > > N1 SDP that is not optimal. Rework in meson build system for ARM SoCs
> > > is planned so I have chosen not to add meson configuration for this
> > > 19.11 patch.
> > >
> > > Vimal Chungath (1):
> > > config: add Graviton2(arm64) defconfig
> > >
> > > config/defconfig_arm64-graviton2-linux-gcc | 1 +
> > > config/defconfig_arm64-graviton2-linuxapp-gcc | 13 +++++++++++
> > > config/defconfig_graviton2 | 1 +
> > > mk/machine/graviton2/rte.vars.mk | 33 +++++++++++++++++++++++++++
> > > 4 files changed, 48 insertions(+)
> > > create mode 120000 config/defconfig_arm64-graviton2-linux-gcc
> > > create mode 100644 config/defconfig_arm64-graviton2-linuxapp-gcc
> > > create mode 120000 config/defconfig_graviton2
> > > create mode 100644 mk/machine/graviton2/rte.vars.mk
> >
> > Hi,
> >
> > Is this adding support for a new driver for 19.11? I don't see it in
> > the main branch?
>
> Hi Luca,
>
> This patch is adding optimal build flags for Graviton2 SoC.
> No new driver is being added. Main branch is no longer accepting make build
> patches as it is deprecated. For 19.11, I assume make is still the default.
>
> This is the meson patch in review for main branch:
> https://patches.dpdk.org/patch/76981/
>
> Regards,
> Vimal
I see - normally we are careful with new feature/support in LTS
branches, but this seems self-contained enough to be very low risk so
it seems acceptable to me. But Meson is fully supported, so please
update the patchset so that it applies to both build systems.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-10-07 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 18:50 [dpdk-stable] [19.11] [PATCH 0/1] Add Graviton2(arm64) build configuration Vimal Chungath
2020-10-05 18:50 ` [dpdk-stable] [19.11] [PATCH 1/1] config: add Graviton2(arm64) defconfig Vimal Chungath
2020-10-07 3:02 ` Honnappa Nagarahalli
2020-10-06 8:12 ` [dpdk-stable] [19.11] [PATCH 0/1] Add Graviton2(arm64) build configuration Luca Boccassi
2020-10-06 18:44 ` [dpdk-stable] [19.11] [PATCH 1/1] config: add Graviton2(arm64) defconfig Vimal Chungath
2020-10-07 9:18 ` Luca Boccassi [this message]
2020-10-07 22:56 ` Vimal Chungath
2020-10-08 4:40 ` Honnappa Nagarahalli
2020-10-07 22:59 ` [dpdk-stable] [19.11] [PATCH v2 0/1] Add Graviton2(arm64) build configuration Vimal Chungath
2020-10-07 22:59 ` [dpdk-stable] [19.11] [PATCH v2 1/1] config: add Graviton2(arm64) defconfig Vimal Chungath
2020-10-08 4:45 ` Honnappa Nagarahalli
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=c2bf394e7e38bde86d66d6c34387de12a1ae6da0.camel@debian.org \
--to=bluca@debian.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=alisaidi@amazon.com \
--cc=bruce.richardson@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vcchunga@amazon.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).