From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Jerry Hao OS <jerryhao@os.amperecomputing.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/1] build: add emag(arm64) platform and default config
Date: Thu, 12 Sep 2019 05:45:47 +0000 [thread overview]
Message-ID: <BN8PR18MB24174718FD3C795653B99E2BC8B00@BN8PR18MB2417.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190912045023.4564-2-jerryhao@os.amperecomputing.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Jerry Hao OS
> Sent: Thursday, September 12, 2019 10:22 AM
> To: thomas@monjalon.net
> Cc: dev@dpdk.org; Jerry Hao OS <jerryhao@os.amperecomputing.com>
> Subject: [dpdk-dev] [PATCH 1/1] build: add emag(arm64) platform and
> default config
>
> This patch is to add the emag default CACHE_LINE_SIZE
> settings and ARCH variable definitions
>
> Signed-off-by: Jerry Hao OS <jerryhao@os.amperecomputing.com>
> ---
> config/defconfig_arm64-emag-linux-gcc | 1 +
> config/defconfig_arm64-emag-linuxapp-gcc | 8 ++++++
> mk/machine/emag/rte.vars.mk | 31 ++++++++++++++++++++++++
> 3 files changed, 40 insertions(+)
> create mode 120000 config/defconfig_arm64-emag-linux-gcc
> create mode 100644 config/defconfig_arm64-emag-linuxapp-gcc
> create mode 100644 mk/machine/emag/rte.vars.mk
Add meson build support as well. See config/arm/*
> +
> +# ARCH =
> +# CROSS =
> +# MACHINE_CFLAGS =
> +# MACHINE_LDFLAGS =
> +# MACHINE_ASFLAGS =
> +# CPU_CFLAGS =
> +# CPU_LDFLAGS =
> +# CPU_ASFLAGS =
> +
> +MACHINE_CFLAGS += -march=armv8-a+crc+crypto
Is emag platform is only armv8? If it is supports lse then add that as well.
See mk/machine/octeontx2/rte.vars.mk as example
If it has dedicated mcpu support then add the following
MACHINE_CFLAGS += $(call rte_cc_has_argument, -mcpu=your_cpu)
> --
> 2.17.1
next prev parent reply other threads:[~2019-09-12 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 4:51 [dpdk-dev] [PATCH 0/1] " Jerry Hao OS
2019-09-12 4:51 ` [dpdk-dev] [PATCH 1/1] " Jerry Hao OS
2019-09-12 5:45 ` Jerin Jacob Kollanukkaran [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-12 8:52 [dpdk-dev] [PATCH 0/1] " Jerry Hao OS
2019-09-12 8:52 ` [dpdk-dev] [PATCH 1/1] " Jerry Hao OS
2019-09-12 9:31 ` Gavin Hu (Arm Technology China)
2019-09-12 16:25 ` Jerin Jacob
2019-09-12 2:44 [dpdk-dev] [PATCH 0/1] " Jerry Hao OS
2019-09-12 2:44 ` [dpdk-dev] [PATCH 1/1] " Jerry Hao OS
2019-09-12 2:30 [dpdk-dev] [PATCH 0/1] " Jerry Hao OS
2019-09-12 2:30 ` [dpdk-dev] [PATCH 1/1] build: " Jerry Hao OS
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=BN8PR18MB24174718FD3C795653B99E2BC8B00@BN8PR18MB2417.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerryhao@os.amperecomputing.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).