From: David Hildenbrand <david@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>, qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Heiko Carstens <hca@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org
Subject: Re: [PATCH v2 0/4] s390x/tcg: fix booting Linux kernels compiled with clang-11 and clang-12
Date: Mon, 11 Jan 2021 10:14:33 +0100 [thread overview]
Message-ID: <231a06cf-08e5-4d4e-9e10-f535e18463c7@redhat.com> (raw)
In-Reply-To: <466de7db-d2bd-4091-5f62-f49c8e4d872c@roeck-us.net>
On 08.01.21 20:21, Guenter Roeck wrote:
> On 1/8/21 5:20 AM, David Hildenbrand wrote:
>> This series fixes booting current upstream Linux kernel compiled by
>> clang-11 and clang-12 under TCG.
>>
>> Decided to pull in already separatly sent patches. The last patch is
>> not required to fix the boot issues, but related to patch #3.
>>
>> Latest version of the patches available at:
>> git@github.com:davidhildenbrand/qemu.git clang
>>
>> v1 -> v2:
>> - Add 's390x/tcg: Don't ignore content in r0 when not specified via "b" or
>> "x"'
>> - Add 's390x/tcg: Ignore register content if b1/b2 is zero when handling
>> EXEUTE'
>> - "s390x/tcg: Fix ALGSI"
>> -- Fixup subject
>> - "s390x/tcg: Fix RISBHG"
>> -- Rephrase description, stating that it fixes clang-11
>>
>> David Hildenbrand (4):
>> s390x/tcg: Fix ALGSI
>> s390x/tcg: Fix RISBHG
>> s390x/tcg: Only ignore content in r0 when specified via "b" or "x"
>> s390x/tcg: Ignore register content if b1/b2 is zero when handling
>> EXECUTE
>>
>> target/s390x/insn-data.def | 10 +++++-----
>> target/s390x/mem_helper.c | 4 ++--
>> target/s390x/translate.c | 33 +++++++++++++++++----------------
>> 3 files changed, 24 insertions(+), 23 deletions(-)
>>
>
> FWIW, for the series, with gcc 8.3.0 and 10.2.0, booting Linux kernel
> v5.11-rc2-178-gf5e6c330254a:
>
> Tested-by: Guenter Roeck <linux@roeck-us.net>
>
> Guenter
>
Thanks Guenter, appreciated!
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2021-01-11 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 13:20 [PATCH v2 0/4] s390x/tcg: fix booting Linux kernels compiled with clang-11 and clang-12 David Hildenbrand
2021-01-08 13:20 ` [PATCH v2 1/4] s390x/tcg: Fix ALGSI David Hildenbrand
2021-01-08 19:33 ` Richard Henderson
2021-01-08 13:20 ` [PATCH v2 2/4] s390x/tcg: Fix RISBHG David Hildenbrand
2021-01-08 19:38 ` Richard Henderson
2021-01-08 13:20 ` [PATCH v2 3/4] s390x/tcg: Only ignore content in r0 when specified via "b" or "x" David Hildenbrand
2021-01-08 19:43 ` Richard Henderson
2021-01-08 13:20 ` [PATCH v2 4/4] s390x/tcg: Ignore register content if b1/b2 is zero when handling EXECUTE David Hildenbrand
2021-01-08 19:47 ` Richard Henderson
2021-01-10 10:11 ` Thomas Huth
2021-01-08 19:00 ` [PATCH v2 0/4] s390x/tcg: fix booting Linux kernels compiled with clang-11 and clang-12 Nick Desaulniers via
2021-01-08 19:21 ` Guenter Roeck
2021-01-11 9:14 ` David Hildenbrand [this message]
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=231a06cf-08e5-4d4e-9e10-f535e18463c7@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.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 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).