From: Vasily Gorbik <gor@linux.ibm.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: clang-built-linux <clang-built-linux@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: LKML: Vasily Gorbik: [GIT PULL] s390 patches for the 5.6 merge window
Date: Mon, 10 Feb 2020 18:58:37 +0100 [thread overview]
Message-ID: <your-ad-here.call-01581357517-ext-6250@work.hours> (raw)
In-Reply-To: <CAKwvOdm+1bMq-uZxe96HViKLzT7jRyxdS68KLyOXhMm2hM9F5w@mail.gmail.com>
On Fri, Feb 07, 2020 at 10:22:20PM +0000, Nick Desaulniers wrote:
> + Vasily for real
>
> On Fri, Feb 7, 2020, 11:02 PM Nick Desaulniers <ndesaulniers@google.com>
> wrote:
>
> > https://lkml.org/lkml/2020/1/28/1141
> >
> > Yo, what's up with clang 10 support?
I believe s390 kernel had limited clang build support since about 5.2
(with jump labels and ftrace disabled), thanks to contributions from Arnd
Bergmann. With asm goto support in clang 9 and now everything for ftrace
in place in clang 10 s390 kernel should be in a good shape feature wise
(including KASAN). At this stage clang based tooling is the main interest.
> >
> > Can I boot this in qemu?
> >
qemu tcg seems to work fine for gcc built s390 kernels. While clang built
kernels run smoothly natively and with accel=kvm there is still something
to be fixed for accel=tcg (kernel fails to boot on both s390 and x86).
next parent reply other threads:[~2020-02-10 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKwvOdkCtyGPeO2kNQSJ3adX6t6k46tf3Au-P06c1G3McRE2KQ@mail.gmail.com>
[not found] ` <CAKwvOdm+1bMq-uZxe96HViKLzT7jRyxdS68KLyOXhMm2hM9F5w@mail.gmail.com>
2020-02-10 17:58 ` Vasily Gorbik [this message]
2020-02-10 18:30 ` LKML: Vasily Gorbik: [GIT PULL] s390 patches for the 5.6 merge window David Hildenbrand
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=your-ad-here.call-01581357517-ext-6250@work.hours \
--to=gor@linux.ibm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.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