[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNPxMo0sNmkbMHmVYn=WJJwtmYR03ZtFDyPhmiMuR1ug=w@mail.gmail.com>
Date: Wed, 3 Jun 2020 15:32:57 +0200
From: Marco Elver <elver@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"the arch/x86 maintainers" <x86@...nel.org>,
"Paul E. McKenney" <paulmck@...nel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
LKML <linux-kernel@...r.kernel.org>,
Will Deacon <will@...nel.org>,
Dmitry Vyukov <dvyukov@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Andrey Konovalov <andreyknvl@...gle.com>
Subject: Re: [PATCH 0/9] x86/entry fixes
On Wed, 3 Jun 2020 at 14:18, Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Wed, Jun 03, 2020 at 02:08:57PM +0200, Marco Elver wrote:
>
> > What is the .config you used? I somehow can't reproduce. I've applied
> > the patches on top of -tip/master.
>
> So tip/master, my patches, your patches, this series.
>
> $ make CC=/opt/llvm/bin/clang O=defconfig-build/ -j80 -s bzImage
>
> is what I used, with the below config.
>
Thanks, can reproduce now. So far I haven't found any indication that
there is a missing check in Clang's instrumentation passes somewhere.
I'm a bit suspicious because both Clang and GCC have this behaviour.
I'll continue looking.
Thanks,
-- Marco
Powered by blists - more mailing lists