All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <dhildenb@redhat.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Thomas Huth <thuth@redhat.com>, Vasily Gorbik <gor@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v1] s390x/tcg: Fix RISBHG
Date: Thu, 7 Jan 2021 18:27:01 -0500 (EST)	[thread overview]
Message-ID: <B6050D16-4BD3-4355-878F-33E3E7C3A75D@redhat.com> (raw)
In-Reply-To: <CAKwvOdmE=Z9pV4txRw-kpcv5FOSr6eEXfmGnc++R_Vzv8MnRDQ@mail.gmail.com>


> Am 08.01.2021 um 00:21 schrieb Nick Desaulniers <ndesaulniers@google.com>:
> 
> On Thu, Jan 7, 2021 at 3:13 PM David Hildenbrand <david@redhat.com> wrote:
>> 
>> RISBHG is broken and currently hinders clang builds of upstream kernels
>> from booting: the kernel crashes early, while decompressing the image.
>> 
>>  [...]
>>   Kernel fault: interruption code 0005 ilc:2
>>   Kernel random base: 0000000000000000
>>   PSW : 0000200180000000 0000000000017a1e
>>         R:0 T:0 IO:0 EX:0 Key:0 M:0 W:0 P:0 AS:0 CC:2 PM:0 RI:0 EA:3
>>   GPRS: 0000000000000001 0000000c00000000 00000003fffffff4 00000000fffffff0
>>         0000000000000000 00000000fffffff4 000000000000000c 00000000fffffff0
>>         00000000fffffffc 0000000000000000 00000000fffffff8 00000000008e25a8
>>         0000000000000009 0000000000000002 0000000000000008 000000000000bce0
>> 
>> One example of a buggy instruction is:
>> 
>>    17dde:       ec 1e 00 9f 20 5d       risbhg  %r1,%r14,0,159,32
>> 
>> With %r14 = 0x9 and %r1 = 0x7 should result in %r1 = 0x900000007, however,
>> results in %r1 = 0.
>> 
>> Let's interpret values of i3/i4 as documented in the PoP and make
>> computation of "mask" only based on i3 and i4 and use "pmask" only at the
>> very end to make sure wrapping is only applied to the high/low doubleword.
>> 
>> With this patch, I can successfully boot a v5.10 kernel built with
>> clang, and gcc builds keep on working.
>> 
>> Fixes: 2d6a869833d9 ("target-s390: Implement RISBG")
>> Reported-by: Nick Desaulniers <ndesaulniers@google.com>
>> Cc: Guenter Roeck <linux@roeck-us.net>
>> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> ---
>> 
>> This BUG was a nightmare to debug and the code a nightmare to understand.
>> 
>> To make clang/gcc builds boot, the following fix is required as well on
>> top of current master: "[PATCH] target/s390x: Fix ALGSI"
>> https://lkml.kernel.org/r/20210107202135.52379-1-david@redhat.com
> 
> In that case, a huge thank you!!! for this work! ++beers_owed.
> 

:) a kernel build for z13 should work with the (default) „-cpu qemu“ cpu type.

>> 
>> ---
>> target/s390x/translate.c | 18 ++++++++----------
>> 1 file changed, 8 insertions(+), 10 deletions(-)
>> 
>> diff --git a/target/s390x/translate.c b/target/s390x/translate.c
>> index 3d5c0d6106..39e33eeb67 100644
>> --- a/target/s390x/translate.c
>> +++ b/target/s390x/translate.c
>> @@ -3815,22 +3815,23 @@ static DisasJumpType op_risbg(DisasContext *s, DisasOps *o)
>>         pmask = 0xffffffff00000000ull;
>>         break;
>>     case 0x51: /* risblg */
>> -        i3 &= 31;
>> -        i4 &= 31;
>> +        i3 = (i3 & 31) + 32;
>> +        i4 = (i4 & 31) + 32;
>>         pmask = 0x00000000ffffffffull;
>>         break;
>>     default:
>>         g_assert_not_reached();
>>     }
>> 
>> -    /* MASK is the set of bits to be inserted from R2.
>> -       Take care for I3/I4 wraparound.  */
>> -    mask = pmask >> i3;
>> +    /* MASK is the set of bits to be inserted from R2. */
>>     if (i3 <= i4) {
>> -        mask ^= pmask >> i4 >> 1;
>> +        /* [0...i3---i4...63] */
>> +        mask = (-1ull >> i3) & (-1ull << (63 - i4));
>>     } else {
>> -        mask |= ~(pmask >> i4 >> 1);
>> +        /* [0---i4...i3---63] */
>> +        mask = (-1ull >> i3) | (-1ull << (63 - i4));
>>     }
> 
> The expression evaluated looks the same to me for both sides of the
> conditional, but the comments differ. Intentional?

& vs |, so the result differs.

Cheers!

  reply	other threads:[~2021-01-07 23:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 23:13 [PATCH v1] s390x/tcg: Fix RISBHG David Hildenbrand
2021-01-07 23:21 ` Nick Desaulniers via
2021-01-07 23:27   ` David Hildenbrand [this message]
2021-01-08  2:20     ` Nick Desaulniers via
2021-01-08  9:44       ` David Hildenbrand
2021-01-08 10:19         ` David Hildenbrand
2021-01-08 10:36           ` David Hildenbrand
2021-01-08 19:14         ` Nick Desaulniers via

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=B6050D16-4BD3-4355-878F-33E3E7C3A75D@redhat.com \
    --to=dhildenb@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux@roeck-us.net \
    --cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.