From: David Wilder <dwilder@us.ibm.com>
To: aconole@redhat.com, maicolgabriel@hotmail.com,
thomas@monjalon.net, ferruh.yigit@intel.com,
arybchenko@solarflare.com
Cc: dev@dpdk.org, ruifeng.wang@arm.com, david.marchand@redhat.com,
drc@linux.vnet.ibm.com, wilder@us.ibm.com
Subject: [dpdk-dev] [PATCH v2 0/3] add travis ci support for ppc64le
Date: Tue, 18 Feb 2020 17:10:04 -0800 [thread overview]
Message-ID: <20200219011007.8611-1-dwilder@us.ibm.com> (raw)
This patch series adds Travis gcc compilation jobs for ppc64le.
Limitations for ppc64le are similar to arm64 (see commit
31bb45bcfd).
1. Only gcc builds are supported on ppc64le.
2. A container is used, therefor Huge pages are not available.
Unit tests are not run, a single test (test-null) using the
no-huge option is run.
V2: Insures iova-mode is VA when --no-huge is selected.
Removed setting of --iova-mode=VA in test-null.sh.
A Travis build with theses patches can be found here:
https://travis-ci.org/djlwilder/dpdk/builds/652238523
David Wilder (3):
eal/linux: select iova-mode va with no-huge option
devtools: allow test-null.sh to run on ppc64le
ci: add travis ci support for native ppc64le
.travis.yml | 30 ++++++++++++++++++++++++++++++
devtools/test-null.sh | 2 +-
lib/librte_eal/linux/eal/eal.c | 14 ++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
--
2.25.0
next reply other threads:[~2020-02-19 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 1:10 David Wilder [this message]
2020-02-19 1:10 ` [dpdk-dev] [PATCH v2 1/3] eal/linux: select iova-mode va with no-huge option David Wilder
2020-02-19 1:10 ` [dpdk-dev] [PATCH v2 2/3] devtools: allow test-null.sh to run on ppc64le David Wilder
2020-02-19 1:10 ` [dpdk-dev] [PATCH v2 3/3] ci: add travis ci support for native ppc64le David Wilder
2020-02-19 7:55 ` Thomas Monjalon
2020-02-19 13:46 ` David Marchand
2020-02-19 20:32 ` dwilder
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=20200219011007.8611-1-dwilder@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=aconole@redhat.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=ferruh.yigit@intel.com \
--cc=maicolgabriel@hotmail.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=wilder@us.ibm.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).