From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [RFC PATCH v2 2/2] cputlb: implement load_helper_unaligned() for unaligned loads
Date: Thu, 10 Jun 2021 14:41:28 -0700 [thread overview]
Message-ID: <543252e5-0b30-8424-d833-4103ddee3919@linaro.org> (raw)
In-Reply-To: <20210609141010.1066750-3-f4bug@amsat.org>
On 6/9/21 7:10 AM, Philippe Mathieu-Daudé wrote:
> + oi = make_memop_idx(MO_UB, mmu_idx);
> + if (memop_big_endian(op)) {
> + for (i = 0; i < size; ++i) {
> + /* Big-endian load. */
> + uint8_t val8 = helper_ret_ldub_mmu(env, addr + i, oi, retaddr);
> + val |= val8 << (((size - 1) * 8) - (i * 8));
> + }
> + } else {
> + for (i = 0; i < size; ++i) {
> + /* Little-endian load. */
> + uint8_t val8 = helper_ret_ldub_mmu(env, addr + i, oi, retaddr);
> + val |= val8 << (i * 8);
> + }
> + }
This doesn't quite work. You can't just call helper_ret_ldub_mmu, as the other
option is full_ldub_code. So, at present you've broken unaligned code loads.
We also need noinline markup for clang, like we do for helper_ret_stb_mmu.
I've no proof of that, but it certainly makes sense to record how we expect the
inline loop to be resolved.
Finally, you have to use uint64_t for val8, otherwise the shift fails for size
== 8.
I'll fix these up and see how things go.
r~
next prev parent reply other threads:[~2021-06-10 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:10 [RFC PATCH v2 0/2] cputlb: implement load_helper_unaligned() for unaligned loads Philippe Mathieu-Daudé
2021-06-09 14:10 ` [PATCH v2 1/2] accel/tcg/cputlb: Extract load_helper_unaligned() from load_helper() Philippe Mathieu-Daudé
2021-06-09 14:10 ` [RFC PATCH v2 2/2] cputlb: implement load_helper_unaligned() for unaligned loads Philippe Mathieu-Daudé
2021-06-10 21:41 ` Richard Henderson [this message]
2021-06-10 22:13 ` Mark Cave-Ayland
2021-06-09 16:09 ` [RFC PATCH v2 0/2] " Mark Cave-Ayland
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=543252e5-0b30-8424-d833-4103ddee3919@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@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).