From: Peter Maydell <peter.maydell@linaro.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] target-arm: Move VLD/VST multiple into helper functions
Date: Sat, 4 Jun 2011 11:01:20 +0100 [thread overview]
Message-ID: <BANLkTinHW8perk2OGDF4WU0Syo=rV+Pkeg@mail.gmail.com> (raw)
In-Reply-To: <20110603204722.GE14583@volta.aurel32.net>
On 3 June 2011 21:47, Aurelien Jarno <aurelien@aurel32.net> wrote:
> Does this patch fixes a real issue (ie most probably a crash), or it is
> just to make the arm target compliant with the README?
I haven't actually generated a test case which would make qemu
abort, but it shouldn't be hard to do so.
> Two remarks there:
> - The guidance in tcg/README is probably true for complex helpers in the
> sense of doing a lot of logic/arithmetic operations for which the TCG
> instruction set if not really rich and for which the compiler can do
> a lot better. When the instruction is emulated mostly by load/store
> ops, there isn't much possible optimizations left.
Yes. The 96 op limit to avoid overrunning the buffer is a hard
one, though.
> - Your patch calls the slow version of the _mmu functions, which doesn't
> use the QEMU TLB. It is therefore normal to expect a slow down.
...even for linux-user mode? That doesn't use softmmu...
Anyway, this patch is on my list to rework when I can figure
out what the right approach to it is.
-- PMM
next prev parent reply other threads:[~2011-06-04 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:52 [Qemu-devel] [PATCH] target-arm: Move VLD/VST multiple into helper functions Peter Maydell
2011-04-28 11:31 ` Peter Maydell
2011-05-02 16:01 ` Peter Maydell
2011-06-03 20:47 ` Aurelien Jarno
2011-06-04 10:01 ` Peter Maydell [this message]
2011-06-06 7:18 ` riku voipio
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='BANLkTinHW8perk2OGDF4WU0Syo=rV+Pkeg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.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).