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: Thu, 6 Mar 2014 17:04:05 +0100 [thread overview]
Message-ID: <20140306160404.GO20660@jannau.net> (raw)
In-Reply-To: <8738ivd074.fsf@linaro.org>
On 2014-03-06 11:40:47 +0000, Alex Bennée wrote:
>
> Janne Grunau <j@jannau.net> writes:
>
> > On 2014-02-25 15:54:37 +0000, Alex Bennée wrote:
> >>
> <snip>
> >> Have you got the log file "unsupported" line? I seem to recall you did
> >> ping me but maybe it was just on IRC? I just want to make sure I
> >> do the right ones. I'm working on this now.
> >
> > We spoke on irc about it. a quick test commenting unsupported
> > instructions out revealed that rshrn/2, sqrshrun and shrn/2 are
> > the only NEON instructions used in libav still missing support
> > in qemu master. Unsoppurted lines from qemu master 0459650d94d1
> > below.
> >
> > target-arm/translate-a64.c:6884: unsupported instruction encoding 0x0f0a8e10 at pc=00000000008632c8
> > target-arm/translate-a64.c:6884: unsupported instruction encoding 0x2f0b8f9c at pc=0000000000865764
> > target-arm/translate-a64.c:6884: unsupported instruction encoding 0x0f0a8610 at pc=0000000000863afc
>
> I've just pushed support for the various shrn opcodes to:
>
> https://github.com/stsquad/qemu/tree/ajb-a64-working
Thanks, just testing it and it seems to work as expected.
> I suspect if libav uses them heavily there could be some optimisation
> to be made as the narrow operations make heavy use of helpers to do the
> saturation stuff.
The saturating shift is not that heavily used and I don't care much as
long as qemu is an order of magnitude faster than ARM's foundation model
and much easier to handle than Apple hardware.
Janne
next prev parent reply other threads:[~2014-03-06 16:04 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
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 [this message]
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=20140306160404.GO20660@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).