From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com
Cc: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Subject: [PATCH OSSTEST] Add arm64 build jobs
Date: Thu, 27 Mar 2014 13:05:12 +0000 [thread overview]
Message-ID: <1395925512-22809-1-git-send-email-ian.campbell@citrix.com> (raw)
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
We have no arm64 hardware in the test pool right now. I have tested this on an
xgene on my desk using the same principal as the "army" arm32 build server
(i.e. a static build-only box). As it happens that uses openSUSE 13.1 as the
root filesystem since Debian doesn't have a full aarch64 port yet, however for
a build-only box that appears to be sufficient.
I'm not sure if it is worth accepting this patch right now, the jobs will all
fail at the first hurdle (host assignment).
---
mfi-common | 14 +++++++++-----
ts-kernel-build | 1 +
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/mfi-common b/mfi-common
index 598aa02..6c49e7d 100644
--- a/mfi-common
+++ b/mfi-common
@@ -40,12 +40,12 @@ create_build_jobs () {
local enable_ovmf
local build_hostflags
- for arch in ${BUILD_ARCHES- i386 amd64 armhf }; do
+ for arch in ${BUILD_ARCHES- i386 amd64 armhf arm64 }; do
if [ "x$arch" = xdisable ]; then continue; fi
case "$arch" in
- armhf)
+ armhf|arm64)
case "$branch" in
linux-3.0) continue;;
linux-3.4) continue;;
@@ -163,7 +163,7 @@ create_build_jobs () {
revision_linuxfirmware=$REVISION_LINUXFIRMWARE
case "$arch" in
- armhf) continue;; # don't do any other kernel builds
+ armhf|arm64) continue;; # don't do any other kernel builds
esac
if [ "x$REVISION_LINUX_OLD" != xdisable ]; then
@@ -226,13 +226,16 @@ test_matrix_iterate () {
*) onetoolstack=xl ;;
esac
- for xenarch in ${TEST_ARCHES- i386 amd64 armhf } ; do
+ for xenarch in ${TEST_ARCHES- i386 amd64 armhf arm64 } ; do
if [ "x$xenarch" = xdisable ]; then continue; fi
test_matrix_branch_filter_callback || continue
case "$xenarch" in
+ arm64)
+ # No runtime tests yet.
+ continue;;
armhf)
# Arm from 4.3 onwards only
case "$xenbranch" in
@@ -277,13 +280,14 @@ test_matrix_iterate () {
*) echo >&2 "kernkind ? $kern"; exit 1 ;;
esac
- for dom0arch in i386 amd64 armhf; do
+ for dom0arch in i386 amd64 armhf arm64; do
case ${xenarch}_${dom0arch} in
amd64_amd64) ;;
amd64_i386) ;;
i386_i386) ;;
armhf_armhf) ;;
+ arm64_arm64) ;;
*) continue ;;
esac
diff --git a/ts-kernel-build b/ts-kernel-build
index 9d890a7..0bb3a5d 100755
--- a/ts-kernel-build
+++ b/ts-kernel-build
@@ -34,6 +34,7 @@ my $makeflags= get_host_property($ho, 'build make flags', '-j4');
my $archparms = {
'armhf' => { DefConfig => 'multi_v7_defconfig', KernelImage => 'arch/arm/boot/zImage' },
+ 'arm64' => { DefConfig => 'defconfig', KernelImage => 'arch/arm64/boot/Image' },
'i386' => { DefConfig => 'defconfig', KernelImage => 'arch/x86/boot/bzImage' },
'amd64' => { DefConfig => 'defconfig', KernelImage => 'arch/x86/boot/bzImage' }
};
--
1.9.0
reply other threads:[~2014-03-27 13:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1395925512-22809-1-git-send-email-ian.campbell@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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).