qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Janne Grunau <j@jannau.net>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	linaro-dev <linaro-dev@lists.linaro.org>,
	Michael Matz <matz@suse.de>, Alexander Graf <agraf@suse.de>,
	"linaro-toolchain@lists.linaro.org"
	<linaro-toolchain@lists.linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Wook Wookey <wookey@linaro.org>,
	Christoffer Dall <Christoffer.Dall@linaro.org>
Subject: Re: [Qemu-devel] Call for testing QEMU aarch64-linux-user emulation
Date: Mon, 24 Feb 2014 14:01:17 +0100	[thread overview]
Message-ID: <20140224130117.GC6747@jannau.net> (raw)
In-Reply-To: <87sirhyi1b.fsf@linaro.org>

Hi,

On 2014-02-17 13:40:00 +0000, Alex Bennée wrote:
> 
> After a solid few months of work the QEMU master branch [1] has now reached
> instruction feature parity with the suse-1.6 [6] tree that a lot of people
> have been using to build various aarch64 binaries. In addition to the
> SUSE work we have fixed numerous edge cases and finished off classes of
> instructions. All instructions have been verified with Peter's RISU
> random instruction testing tool. I have also built and run many
> packages as well as built gcc and passed most of the aarch64 specific tests.
> 
> I've tested against the following aarch64 rootfs:
>     * SUSE [2]
>     * Debian [3]
>     * Ubuntu Saucy [4]

I'm running Libav's test suite (https://fate.libav.org/?arch=aarch64&comment=qemu)
using a Gentoo crossdev sysroot.

> In my tree the remaining insns that the GCC aarch64 tests need to
> implement are:
>     FRECPE
>     FRECPX
>     CLS (2 misc variant)
>     CLZ (2 misc variant)
>     FSQRT
>     FRINTZ
>     FCVTZS
> 
> Which I'm currently working though now. However for most build tasks I
> expect the instructions in master [1] will be enough.

Qemu master is enough to pass the tests with libav built with gcc 4.8.2,
clang 3.3 and 3.4 (clang 3.4 build only with -O1, it fails otherwise).

> Feedback I'm interested in
> ==========================
> 
> * Any instruction failure (please include the log line with the
>   unsupported message)

Neon support is not complete enough to run the hand written neon
assembler optimizations in libav. Currently failing on narrowing shifts.

> * Any aarch64 specific failures (i.e. not generic QEMU threading flakeiness).

Just as a note, qemu-arm64 from the suse tree didn't show any threading
issues with the libav test suite while qemu-aarch64 from master failed
with a probability of ~10% running the same binary.
 
> Many thanks to the SUSE guys for getting the aarch64 train rolling. I
> hope your happy with the final result ;-)

I'm happy, qemu master runs the libav test suite around 30% faster.
Thanks to everyone involved.

Janne

  reply	other threads:[~2014-02-24 13:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 13:40 [Qemu-devel] Call for testing QEMU aarch64-linux-user emulation Alex Bennée
2014-02-24 13:01 ` Janne Grunau [this message]
2014-02-25 15:54   ` Alex Bennée
2014-02-25 17:11     ` Janne Grunau
2014-03-06 11:40       ` Alex Bennée
2014-03-06 16:04         ` Janne Grunau
2014-02-24 20:58 ` Dann Frazier
2014-02-25  8:39   ` Alex Bennée
2014-02-25  8:49     ` Andreas Färber
2014-02-25 13:33       ` Michael Matz
2014-02-25 13:46         ` Peter Maydell
2014-02-25 14:56           ` Michael Matz
2014-02-28 14:12             ` Alex Bennée
2014-02-28 14:21               ` Peter Maydell
2014-02-28 14:27                 ` Alexander Graf
2014-02-28 14:49                   ` Peter Maydell
2014-02-28 17:08                     ` Alex Bennée
2014-02-28 17:17                       ` Peter Maydell
2014-02-26 22:06     ` Dann Frazier
2014-02-27 13:20       ` Michael Matz
2014-02-27 19:47         ` Dann Frazier
2014-03-14 14:20         ` Peter Maydell
2014-03-09 23:37     ` Dann Frazier
2014-03-09 23:51       ` Peter Maydell
2014-03-10 11:28         ` Alex Bennée
2014-03-10 11:45           ` Peter Maydell
2014-03-10 13:56           ` Michael Matz

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=20140224130117.GC6747@jannau.net \
    --to=j@jannau.net \
    --cc=Christoffer.Dall@linaro.org \
    --cc=agraf@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=matz@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wookey@linaro.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).