From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
"Gavin.Hu@arm.com" <Gavin.Hu@arm.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"yskoh@mellanox.com" <yskoh@mellanox.com>,
"Phil.Yang@arm.com" <Phil.Yang@arm.com>
Cc: "nd@arm.com" <nd@arm.com>,
"russell@mellanox.com" <russell@mellanox.com>,
"mrosenbluth@mellanox.com" <mrosenbluth@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Default cacheline size for ARM
Date: Fri, 1 Feb 2019 17:16:25 +0000 [thread overview]
Message-ID: <89542c89a3f70a23abc81e78d20e46b2b24d8c15.camel@marvell.com> (raw)
In-Reply-To: <AM6PR08MB3672143DEE893432A6B7320698910@AM6PR08MB3672.eurprd08.prod.outlook.com>
On Thu, 2019-01-31 at 18:09 +0000, Honnappa Nagarahalli wrote:
> + Phil and Hemant
>
> <snip>
>
> > > > > > Yes, we need to be inline with any other package. My
> > > > > > understanding is that the image will be same for v8,v9,v10
> > > > > > (any
> > > > > > input from distro engineers will help here). So, my
> > > > > > question is,
> > > > > > should the config file/name used by distros contain
> > > > > > anything
> > > > > > specific to armv8?
> > > > > Jerin, after following [1], I am not unable to understand
> > > > > when the
> > > > > file config/arm/arm64_armv8_linuxapp_gcc gets used. Is this
> > > > > file
> > > > > required?
> > > >
> > > > If I understand it correctly, only for cross compiling on x86.
> > > > distro folks build the generic image on arm64 with
> > > > -Dmachine=default
> > > > for arm64.
> > > I thought for cross compilation we have target specific config
> > > files
> > > in config/arm. For ex: arm64_dpaa2_linuxapp_gcc,
> > > arm64_thunderx_linuxapp_gcc
> >
> > Yes. config/arm/arm64_armv8_linuxapp_gcc will be used for cross
> > compile
> > arm64 image, equivalent to config/defconfig_arm64-armv8a-linuxapp-
> > gcc
> > in cross compiling domain for meson.
> >
> Following is my understanding:
> 1) Distro folks build the generic image on arm64 with
> -Dmachine=default for arm64 (
> http://mails.dpdk.org/archives/dev/2019-January/123272.html)
> 2) Target specific builds and cross compilation is done using target
> specific configuration files (for ex:
> config/arm/arm64_dpaa2_linuxapp_gcc etc)
>
> Are you saying, we need a cross compile mechanism to generate generic
> arm64 image (that would work across all Arm platforms)?
> Do you have any use cases in mind for this?
# I was thinking, Not everyone has access to arm64 machine so having
one generic cross compile target can function as build sanity check for
arm64 on x86 machines.
# The _buildroot_ kind of tiny embedded rootfs can not have gcc on
target, so this config will be useful for such build enablement as
default option.
>
> > > > > 1.
> > > > > http://mails.dpdk.org/archives/dev/2019-January/123272.html
prev parent reply other threads:[~2019-02-01 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 19:59 [dpdk-dev] " Yongseok Koh
2019-01-05 5:14 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-01-05 22:47 ` Honnappa Nagarahalli
2019-01-06 7:56 ` Jerin Jacob Kollanukkaran
2019-01-14 7:47 ` Honnappa Nagarahalli
2019-01-14 8:05 ` Jerin Jacob Kollanukkaran
2019-01-16 1:57 ` Honnappa Nagarahalli
2019-01-18 5:50 ` Honnappa Nagarahalli
2019-01-23 9:05 ` Jerin Jacob Kollanukkaran
2019-01-23 16:28 ` Honnappa Nagarahalli
2019-01-28 12:56 ` Jerin Jacob Kollanukkaran
2019-01-31 18:09 ` Honnappa Nagarahalli
2019-02-01 17:16 ` Jerin Jacob Kollanukkaran [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=89542c89a3f70a23abc81e78d20e46b2b24d8c15.camel@marvell.com \
--to=jerinj@marvell.com \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Phil.Yang@arm.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=mrosenbluth@mellanox.com \
--cc=nd@arm.com \
--cc=russell@mellanox.com \
--cc=yskoh@mellanox.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).