From: "Alex Bennée" <alex.bennee@linaro.org>
To: linaro-dev <linaro-dev@lists.linaro.org>,
"linaro-toolchain@lists.linaro.org"
<linaro-toolchain@lists.linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Michael Matz <matz@suse.de>, Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
Wook Wookey <wookey@linaro.org>,
Christoffer Dall <Christoffer.Dall@linaro.org>
Subject: [Qemu-devel] Call for testing QEMU aarch64-linux-user emulation
Date: Mon, 17 Feb 2014 13:40:00 +0000 [thread overview]
Message-ID: <87sirhyi1b.fsf@linaro.org> (raw)
Hi,
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]
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.
If you want the latest instructions working their way to mainline you
are free to use my tree [5] which currently has:
* Additional NEON/SIMD instructions
* sendmsg syscall
* Improved helper scripts for setting up binfmt_misc
* The ability to set QEMU_LOG_FILENAME to /path/to/something-%d.log
- this is useful when tests are failing N-levels deep as %d is
replaced with the pid
Feedback I'm interested in
==========================
* Any instruction failure (please include the log line with the
unsupported message)
* Any aarch64 specific failures (i.e. not generic QEMU threading flakeiness).
If you need to catch me in real time I'm available on #qemu (stsquad)
and #linaro-virtualization (ajb-linaro).
Many thanks to the SUSE guys for getting the aarch64 train rolling. I
hope your happy with the final result ;-)
Cheers,
--
Alex Bennée
QEMU/KVM Hacker for Linaro
[1] git://git.qemu.org/qemu.git master
[2] http://download.opensuse.org/ports/aarch64/distribution/13.1/appliances/openSUSE-13.1-ARM-JeOS.aarch64-rootfs.aarch64-1.12.1-Build32.1.tbz
[3] http://people.debian.org/~wookey/bootstrap/rootfs/debian-unstable-arm64.tar.gz
[4] http://people.debian.org/~wookey/bootstrap/rootfs/saucy-arm64.tar.gz
[5] https://github.com/stsquad/qemu/tree/ajb-a64-working
[6] https://github.com/susematz/qemu/tree/aarch64-1.6
next reply other threads:[~2014-02-17 13:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 13:40 Alex Bennée [this message]
2014-02-24 13:01 ` [Qemu-devel] Call for testing QEMU aarch64-linux-user emulation Janne Grunau
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=87sirhyi1b.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=Christoffer.Dall@linaro.org \
--cc=agraf@suse.de \
--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).