From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
richard.henderson@linaro.org,
"open list:S390 TCG CPUs" <qemu-s390x@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH] target/s390x: don't double ld_code() when reading instructions
Date: Tue, 12 Oct 2021 10:31:28 +0100 [thread overview]
Message-ID: <20211012093128.3909859-1-alex.bennee@linaro.org> (raw)
For the 4 byte instruction case we started doing an ld_code2 and then
reloaded the data with ld_code4 once it was identified as a 4 byte op.
This is confusing for the plugin hooks which are expecting to see
simple sequential loading so end up reporting a malformed 6 byte
instruction buffer. While we are at it lets clean up some of the
shifts with nice deposit/extrac calls.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
target/s390x/tcg/translate.c | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/target/s390x/tcg/translate.c b/target/s390x/tcg/translate.c
index a2d6fa5cca..7fc870bbb9 100644
--- a/target/s390x/tcg/translate.c
+++ b/target/s390x/tcg/translate.c
@@ -6273,21 +6273,20 @@ static const DisasInsn *extract_insn(CPUS390XState *env, DisasContext *s)
/* Extract the values saved by EXECUTE. */
insn = s->ex_value & 0xffffffffffff0000ull;
- ilen = s->ex_value & 0xf;
- op = insn >> 56;
+ ilen = extract64(s->ex_value, 0, 8);
+ op = extract64(insn, 56, 8);
} else {
- insn = ld_code2(env, s, pc);
- op = (insn >> 8) & 0xff;
+ insn = deposit64(0, 48, 16, ld_code2(env, s, pc));
+ op = extract64(insn, 56, 8);
ilen = get_ilen(op);
switch (ilen) {
case 2:
- insn = insn << 48;
break;
case 4:
- insn = ld_code4(env, s, pc) << 32;
+ insn = deposit64(insn, 32, 16, ld_code2(env, s, pc + 2));
break;
- case 6:
- insn = (insn << 48) | (ld_code4(env, s, pc + 2) << 16);
+ case 6:
+ insn = deposit64(insn, 16, 32, ld_code4(env, s, pc + 2));
break;
default:
g_assert_not_reached();
--
2.30.2
next reply other threads:[~2021-10-12 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 9:31 Alex Bennée [this message]
2021-10-12 12:07 ` [RFC PATCH] target/s390x: don't double ld_code() when reading instructions Richard Henderson
2021-10-12 12:10 ` Richard Henderson
2021-10-12 14:52 ` Alex Bennée
2021-10-12 15:38 ` Richard Henderson
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=20211012093128.3909859-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/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).