All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 5/5] travis.yml: Compile on arm64, too
Date: Thu, 10 Oct 2019 11:53:40 +0100	[thread overview]
Message-ID: <8736g0na6j.fsf@linaro.org> (raw)
In-Reply-To: <ce024ffd-1b7f-39e0-b754-dc98a2a7513c@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> On 09/10/2019 21.06, Philippe Mathieu-Daudé wrote:
>> On 10/9/19 7:07 PM, Thomas Huth wrote:
>>> Travis now features an arm64 build host, so let's check compilation
>>> there, too.
>>>
>>> Unfortunately, there are some quirks:
>>> - block/ssh.c does not compile properly in this environment, so we have
>>>    to use --disable-libssh until that problem is fixed.
>>> - test-util-filemonitor fails, so we can not run the unit tests there
>>> - The file system size seems to be very limited, so the iotest tests
>>>    can't be used and the hd-geo-test fails (thus we can't compile
>>>    x86_64-softmmu here and run "check-qtest" afterwards)
>>> - Compiling seems to be quite a bit slower than on the x86 builders,
>>>    so we better limit the target list to some few architectures.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>>   .travis.yml | 6 ++++++
>>>   1 file changed, 6 insertions(+)
>>>
>>> diff --git a/.travis.yml b/.travis.yml
>>> index 0c88e8757b..357ca02890 100644
>>> --- a/.travis.yml
>>> +++ b/.travis.yml
>>> @@ -342,3 +342,9 @@ matrix:
>>>           -
>>> CONFIG="--target-list=xtensa-softmmu,arm-softmmu,aarch64-softmmu,alpha-softmmu"
>>>
>>>           - TEST_CMD="make -j3 check-tcg V=1"
>>>           - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-default"
>>> +
>>> +    # Non-x86 builds:
>>> +    - env:
>>> +        - CONFIG="--disable-libssh
>>> --target-list=aarch64-softmmu,ppc64-softmmu,s390x-softmmu,x86_64-linux-user"
>>>
>>
>> Is aarch64 on aarch64 interesting?
>>
>> Do you know if we can use KVM there?
>
> I don't think that KVM is usable there, but at least this should give us
> some compile coverage for target/arm/kvm.c which we don't get
> otherwise.

We get compile coverage for !x86 kvm from the cross compilers on
shippable. I'm more interested in running tests on !x86.

>
>  Thomas


--
Alex Bennée


  reply	other threads:[~2019-10-10 10:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 17:06 [PATCH 0/5] travis.yml improvements: Update libraries, build with arm64 Thomas Huth
2019-10-09 17:06 ` [PATCH 1/5] travis.yml: Add libvdeplug-dev to compile-test net/vde.c Thomas Huth
2019-10-09 17:06 ` [PATCH 2/5] travis.yml: Use libsdl2 instead of libsdl1.2, and install libsdl2-image Thomas Huth
2019-10-09 17:06 ` [PATCH 3/5] travis.yml: Use newer version of libgnutls and libpng Thomas Huth
2019-10-09 17:07 ` [PATCH 4/5] travis.yml: Fix the ccache lines Thomas Huth
2019-10-09 19:04   ` Philippe Mathieu-Daudé
2019-10-10  9:38     ` Thomas Huth
2019-10-10 11:16       ` Philippe Mathieu-Daudé
2019-10-10 11:29         ` Thomas Huth
2019-10-10 11:51           ` Philippe Mathieu-Daudé
2019-10-09 17:07 ` [PATCH 5/5] travis.yml: Compile on arm64, too Thomas Huth
2019-10-09 19:06   ` Philippe Mathieu-Daudé
2019-10-10  6:55     ` Thomas Huth
2019-10-10 10:53       ` Alex Bennée [this message]
2019-10-10 10:58   ` Daniel P. Berrangé
2019-10-10 11:57     ` Thomas Huth
2019-10-10 13:29       ` Daniel P. Berrangé
2019-10-22 10:41   ` Alex Bennée
2019-10-22 11:19     ` Thomas Huth
2019-10-16 17:56 ` [PATCH 0/5] travis.yml improvements: Update libraries, build with arm64 Alex Bennée
2019-10-21 13:53   ` Thomas Huth
2019-10-21 14:10     ` Philippe Mathieu-Daudé

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=8736g0na6j.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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.