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 v1 0/2] add travis ci support for ppc64le
Date: Thu, 13 Feb 2020 12:24:40 -0800 [thread overview]
Message-ID: <20200213202442.19674-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.
The first patch in the series adjusts parameters for devtools/test-null.sh
as required for ppc64le.
A Travis build with theses two patches can be found here:
https://travis-ci.org/djlwilder/dpdk/builds/650091701
David Wilder (2):
devtools: allow test-null.sh to run on ppc64le
ci: add travis ci support for native ppc64le
.travis.yml | 29 +++++++++++++++++++++++++++++
devtools/test-null.sh | 2 +-
2 files changed, 30 insertions(+), 1 deletion(-)
--
2.25.0
next reply other threads:[~2020-02-13 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 20:24 David Wilder [this message]
2020-02-13 20:24 ` [dpdk-dev] [PATCH v1 1/2] devtools: allow test-null.sh to run on ppc64le David Wilder
2020-02-13 20:32 ` Thomas Monjalon
2020-02-13 20:58 ` dwilder
2020-02-13 22:17 ` Thomas Monjalon
2020-02-13 23:23 ` dwilder
2020-02-14 13:22 ` David Marchand
2020-02-13 20:24 ` [dpdk-dev] [PATCH v1 2/2] ci: add travis ci support for native ppc64le David Wilder
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=20200213202442.19674-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.