From: Stefan Weil <sw@weilnetz.de>
To: Peter Hanzel <hanzelpeter@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Raspbian in QEMU
Date: Wed, 12 Mar 2014 19:56:15 +0100 [thread overview]
Message-ID: <5320ADCF.5000406@weilnetz.de> (raw)
In-Reply-To: <CAD=tUvyP=UPZ2tS9L_9g6cz7veKe_xmT+q53ac9N_fU67bpnBQ@mail.gmail.com>
Am 12.03.2014 19:05, schrieb Peter Hanzel:
> Thanks.
>
> Now it makes sense. Also google now works and led me to
> https://github.com/bavison/arm-mem.
> And there is SETEND used.
>
It might be possible to handle that special case in QEMU without
implementing setend:
That instruction is only used in the implementation of function memcmp.
When TCG detects a setend instruction, it could check whether the
surrounding code has the signature of that memcmp implementation and add
code which calls a memcmp helper function. The setend instruction and
all the following code of memcmp would be handled as if it were a single
special multi byte machine instruction.
Is that special accelerated implementation of memcmp used in lots of ARM
systems, or is it only used for Raspberry PI? From the copyright in
memcpy.S I'd guess that it is RPi specific, so maybe the need for a QEMU
hack is not urgent enough.
Stefan
PS. Link to previous discussion on setend:
https://lists.gnu.org/archive/html/qemu-trivial/2013-08/msg00086.html
I cc Richard because he was / is involved, too.
next prev parent reply other threads:[~2014-03-12 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 9:55 [Qemu-devel] Raspbian in QEMU Peter Hanzel
2014-03-12 15:43 ` Peter Maydell
2014-03-12 18:05 ` Peter Hanzel
2014-03-12 18:56 ` Stefan Weil [this message]
2014-03-12 19:41 ` Richard Henderson
2014-03-12 20:01 ` Peter Maydell
2014-03-20 12:36 ` Paolo Bonzini
2014-03-20 13:08 ` François Revol
2014-03-20 13:21 ` Paolo Bonzini
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=5320ADCF.5000406@weilnetz.de \
--to=sw@weilnetz.de \
--cc=hanzelpeter@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).