From: David Hildenbrand <david@redhat.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Subject: Re: [PATCH 1/2] target/s390x: Fix EXECUTE of relative long instructions
Date: Tue, 14 Mar 2023 10:10:34 +0100 [thread overview]
Message-ID: <09ef41ae-448d-b29a-6352-d86cd6e67362@redhat.com> (raw)
In-Reply-To: <20230313233819.122329-2-iii@linux.ibm.com>
On 14.03.23 00:38, Ilya Leoshkevich wrote:
> The code uses the wrong base for relative addressing: it should use the
> target instruction address and not the EXECUTE's address.
>
> Fix by storing the target instruction address in the new CPUS390XState
> member and loading it from the code generated by in2_ri2().
>
> Reported-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> target/s390x/cpu.h | 1 +
> target/s390x/tcg/mem_helper.c | 1 +
> target/s390x/tcg/translate.c | 10 +++++++++-
> 3 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/target/s390x/cpu.h b/target/s390x/cpu.h
> index 7d6d01325b2..8aaf8dd5a3b 100644
> --- a/target/s390x/cpu.h
> +++ b/target/s390x/cpu.h
> @@ -87,6 +87,7 @@ struct CPUArchState {
> uint64_t cc_vr;
>
> uint64_t ex_value;
> + uint64_t ex_target;
>
> uint64_t __excp_addr;
> uint64_t psa;
> diff --git a/target/s390x/tcg/mem_helper.c b/target/s390x/tcg/mem_helper.c
> index 6835c26dda4..00afae2b640 100644
> --- a/target/s390x/tcg/mem_helper.c
> +++ b/target/s390x/tcg/mem_helper.c
> @@ -2530,6 +2530,7 @@ void HELPER(ex)(CPUS390XState *env, uint32_t ilen, uint64_t r1, uint64_t addr)
> that ex_value is non-zero, which flags that we are in a state
> that requires such execution. */
> env->ex_value = insn | ilen;
> + env->ex_target = addr;
> }
>
> uint32_t HELPER(mvcos)(CPUS390XState *env, uint64_t dest, uint64_t src,
> diff --git a/target/s390x/tcg/translate.c b/target/s390x/tcg/translate.c
> index 811049ea281..fefff95b91c 100644
> --- a/target/s390x/tcg/translate.c
> +++ b/target/s390x/tcg/translate.c
> @@ -5888,7 +5888,15 @@ static void in2_a2(DisasContext *s, DisasOps *o)
>
> static void in2_ri2(DisasContext *s, DisasOps *o)
> {
> - o->in2 = tcg_const_i64(s->base.pc_next + (int64_t)get_field(s, i2) * 2);
> + int64_t delta = (int64_t)get_field(s, i2) * 2;
> +
> + if (unlikely(s->ex_value)) {
> + o->in2 = tcg_temp_new_i64();
> + tcg_gen_ld_i64(o->in2, cpu_env, offsetof(CPUS390XState, ex_target));
> + tcg_gen_addi_i64(o->in2, o->in2, delta);
> + } else {
> + o->in2 = tcg_const_i64(s->base.pc_next + delta);
> + }
> }
> #define SPEC_in2_ri2 0
>
LGTM, hopefully Richard can have another look. Thanks!
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-03-14 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 23:38 [PATCH 0/2] Fix EXECUTE of relative long instructions Ilya Leoshkevich
2023-03-13 23:38 ` [PATCH 1/2] target/s390x: " Ilya Leoshkevich
2023-03-14 9:10 ` David Hildenbrand [this message]
2023-03-14 16:29 ` Richard Henderson
2023-03-13 23:38 ` [PATCH 2/2] tests/tcg/s390x: Add ex-relative-long.c Ilya Leoshkevich
2023-03-14 17:05 ` 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=09ef41ae-448d-b29a-6352-d86cd6e67362@redhat.com \
--to=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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).