qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, Cornelia Huck <cohuck@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v3 4/5] tests/tcg/s390x: Fix EXRL tests
Date: Tue, 12 Jan 2021 08:41:39 +0100	[thread overview]
Message-ID: <fdb64ad0-463a-3a35-e68d-4ce0d0de95b5@redhat.com> (raw)
In-Reply-To: <20210111163845.18148-5-david@redhat.com>

On 11/01/2021 17.38, David Hildenbrand wrote:
> The current EXRL tests crash on real machines: we must not use r0 as a base
> register for trt/trtr, otherwise the content gets ignored. Also, we must
> not use r0 for exrl, otherwise it gets ignored.
> 
> Let's use the "a" constraint so we get a general purpose register != r0.
> For op2, we can simply specify a memory operand directly via "Q" (Memory
> reference without index register and with short displacement).
> 
> Fixes: ad8c851d2e77 ("target/s390x: add EX support for TRT and TRTR")
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>   tests/tcg/s390x/exrl-trt.c  | 8 ++++----
>   tests/tcg/s390x/exrl-trtr.c | 8 ++++----
>   2 files changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/tests/tcg/s390x/exrl-trt.c b/tests/tcg/s390x/exrl-trt.c
> index 3c5323aecb..16711a3181 100644
> --- a/tests/tcg/s390x/exrl-trt.c
> +++ b/tests/tcg/s390x/exrl-trt.c
> @@ -19,7 +19,7 @@ int main(void)
>       }
>       asm volatile(
>           "    j 2f\n"
> -        "1:  trt 0(1,%[op1]),0(%[op2])\n"
> +        "1:  trt 0(1,%[op1]),%[op2]\n"
>           "2:  exrl %[op1_len],1b\n"
>           "    lgr %[r1],%%r1\n"
>           "    lgr %[r2],%%r2\n"
> @@ -27,9 +27,9 @@ int main(void)
>           : [r1] "+r" (r1),
>             [r2] "+r" (r2),
>             [cc] "=r" (cc)
> -        : [op1] "r" (&op1),
> -          [op1_len] "r" (5),
> -          [op2] "r" (&op2)
> +        : [op1] "a" (&op1),
> +          [op1_len] "a" (5),

I think op1_len could still stay with "r" instead of "a" ... OTOH "a" also 
does not hurt here, so:

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2021-01-12  7:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 16:38 [PATCH v3 0/5] s390x/tcg: fix booting Linux kernels compiled with clang-11 and clang-12 David Hildenbrand
2021-01-11 16:38 ` [PATCH v3 1/5] s390x/tcg: Fix ALGSI David Hildenbrand
2021-01-11 16:38 ` [PATCH v3 2/5] s390x/tcg: Fix RISBHG David Hildenbrand
2021-01-11 16:38 ` [PATCH v3 3/5] s390x/tcg: Don't ignore content in r0 when not specified via "b" or "x" David Hildenbrand
2021-01-11 16:38 ` [PATCH v3 4/5] tests/tcg/s390x: Fix EXRL tests David Hildenbrand
2021-01-12  7:41   ` Thomas Huth [this message]
2021-01-12  7:47     ` David Hildenbrand
2021-01-12  8:16       ` Thomas Huth
2021-01-12 10:04         ` David Hildenbrand
2021-01-11 16:38 ` [PATCH v3 5/5] s390x/tcg: Ignore register content if b1/b2 is zero when handling EXECUTE David Hildenbrand
2021-01-12 10:40 ` [PATCH v3 0/5] s390x/tcg: fix booting Linux kernels compiled with clang-11 and clang-12 Cornelia Huck

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=fdb64ad0-463a-3a35-e68d-4ce0d0de95b5@redhat.com \
    --to=thuth@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.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).