From: Ard Biesheuvel <ardb@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: "kernelci-results@groups.io" <kernelci-results@groups.io>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Nicolas Pitre <nico@fluxnic.net>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
Linus Walleij <linus.walleij@linaro.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: next/master bisection: baseline.login on rk3288-rock2-square
Date: Thu, 4 Feb 2021 13:09:42 +0100 [thread overview]
Message-ID: <CAMj1kXH1U72-3i1F=i-FjYrC_mv9S7ypeA835JMubb=-yKjxOg@mail.gmail.com> (raw)
In-Reply-To: <20210204114420.GW1463@shell.armlinux.org.uk>
On Thu, 4 Feb 2021 at 12:45, Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
>
> On Thu, Feb 04, 2021 at 11:32:05AM +0000, Guillaume Tucker wrote:
> > Yes it does fix the issue:
> >
> > https://lava.collabora.co.uk/scheduler/job/3173819
> >
> > with Ard's fix applied to this test branch:
> >
> > https://gitlab.collabora.com/gtucker/linux/-/commits/next-20210203-ard-fix/
> >
> >
> > +clang +Nick
> >
> > It's worth mentioning that the issue only happens with kernels
> > built with Clang. As you can see there are several other arm
> > platforms failing with clang-11 builds but booting fine with
> > gcc-8:
>
> My gut feeling is that it isn't Clang specific - it's likely down to
> the exact code/data placement, how things end up during decompression,
> and exactly what state the cache ends up in.
>
> That certainly was the case with the original regression.
>
Agreed.
So given that my queued fix turns this
cache_clean
cache_off
into this
cache_off
cache_clean
for v7 only, and considering that turning this into
cache_clean
cache_off
cache_clean
(as the diff tested by Guillaume does) fixes the reported issue, it
seems like the safest option to me at this point.
Reverting both patches, one of which has been in mainline since v5.7,
seems unwise to me at this point in the cycle.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-04 12:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <601b773a.1c69fb81.9f381.a32a@mx.google.com>
2021-02-04 8:43 ` next/master bisection: baseline.login on rk3288-rock2-square Guillaume Tucker
2021-02-04 9:07 ` Ard Biesheuvel
2021-02-04 10:06 ` Russell King - ARM Linux admin
2021-02-04 10:27 ` Ard Biesheuvel
2021-02-04 10:33 ` Guillaume Tucker
2021-02-04 11:32 ` Guillaume Tucker
2021-02-04 11:44 ` Russell King - ARM Linux admin
2021-02-04 12:09 ` Ard Biesheuvel [this message]
2021-02-04 15:42 ` Ard Biesheuvel
2021-02-04 15:53 ` Guillaume Tucker
2021-02-04 16:01 ` Ard Biesheuvel
2021-02-04 18:06 ` Nick Desaulniers
2021-02-04 18:12 ` Nathan Chancellor
2021-02-04 18:23 ` Nick Desaulniers
2021-02-04 21:31 ` Guillaume Tucker
2021-02-04 21:50 ` Russell King - ARM Linux admin
2021-02-05 8:21 ` Ard Biesheuvel
2021-02-05 12:05 ` Ard Biesheuvel
2021-02-06 13:10 ` Guillaume Tucker
2021-02-06 13:12 ` Ard Biesheuvel
2021-02-04 21:09 ` Guillaume Tucker
2021-02-04 10:47 ` Russell King - ARM Linux admin
2021-02-04 10:55 ` Ard Biesheuvel
2021-02-04 12:26 ` Marc Zyngier
2021-02-04 14:09 ` Russell King - ARM Linux admin
2021-02-04 14:25 ` Ard Biesheuvel
2021-02-04 14:36 ` Russell King - ARM Linux admin
2021-02-04 15:52 ` Ard Biesheuvel
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='CAMj1kXH1U72-3i1F=i-FjYrC_mv9S7ypeA835JMubb=-yKjxOg@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=geert+renesas@glider.be \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ndesaulniers@google.com \
--cc=nico@fluxnic.net \
/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).