From: Richard Henderson <rth@twiddle.net>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Claudio Fontana <claudio.fontana@huawei.com>,
qemu-stable <qemu-stable@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] tcg/aarch64: Fix tcg_out_qemu_{ld, st} for linux-user
Date: Fri, 28 Aug 2015 22:33:49 -0700 [thread overview]
Message-ID: <55E1443D.1060305@twiddle.net> (raw)
In-Reply-To: <55E08AEE.3060308@suse.de>
On 08/28/2015 09:23 AM, Andreas Färber wrote:
> An otype argument is being inserted as next-to-last argument for the
> function definitions. Same for the softmmu callsites. Only in the *-user
> callsites the argument order is being changed with addr_reg and off_r
> switching order? I don't see why that should be done in this patch. If
> it was wrong before, it should've been done in a separate patch.
It wasn't "wrong" before because it didn't matter before.
The whole point of the patch is that we're changing from
(xD = data_reg, xA = addr_reg, xG = GUEST_BASE)
ldr xD, [xA, xG]
to
ldr xD, [xG, wA, uxtw]
i.e. zero-extending xA during the address formation.
Before this patch, the order of xA and xG doesn't matter; they're both straight
addition operands. After this patch, if we don't switch the argument order
it'll be xG that gets zero-extending GUEST_BASE, which is obviously incorrect.
You'll note that we also switch the argument order for the softmmu case in the
next patch, and for the same reason.
Tomorrow I'll be home and can do any further investigation in depth.
r~
next prev parent reply other threads:[~2015-08-29 5:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 23:47 [Qemu-devel] [PATCH] tcg/aarch64: Fix tcg_out_qemu_{ld, st} for linux-user Andreas Färber
2015-08-28 4:30 ` Richard Henderson
2015-08-28 16:23 ` Andreas Färber
2015-08-29 5:33 ` Richard Henderson [this message]
2015-08-29 6:50 ` Paolo Bonzini
2015-09-01 16:31 ` Andreas Färber
2015-09-01 20:09 ` Richard Henderson
2015-09-02 9:02 ` Paolo Bonzini
2015-09-02 14:26 ` Richard Henderson
2015-09-02 14:38 ` Andreas Färber
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=55E1443D.1060305@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=claudio.fontana@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).