[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171130174834.GC90451@samitolvanen.mtv.corp.google.com>
Date: Thu, 30 Nov 2017 09:48:34 -0800
From: Sami Tolvanen <samitolvanen@...gle.com>
To: Nicholas Piggin <npiggin@...il.com>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Alex Matveev <alxmtvv@...il.com>,
Andi Kleen <ak@...ux.intel.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Greg Hackmann <ghackmann@...gle.com>,
Kees Cook <keescook@...omium.org>,
linux-arm-kernel@...ts.infradead.org,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@...aro.org>,
Michal Marek <michal.lkml@...kovi.net>,
Yury Norov <ynorov@...iumnetworks.com>,
Matthias Kaehlcke <mka@...omium.org>
Subject: Re: [PATCH 5/7] arm64: keep .altinstructions and
.altinstr_replacement
On Thu, Nov 30, 2017 at 11:58:27AM +1000, Nicholas Piggin wrote:
> So yes please if it's not too much trouble, could you remove
> the "gold" name from the generic patch and put it at the front
> of the series with this arm64 patch.
Sure, I'll do this in v2.
> Possibly then you could also do a 3rd patch to allow arm64 to
> select it if it's working with gcc?
These patches only fix the issues I ran into with clang and gold
when testing on a single device. I feel like more testing would
be needed before enabling this by default for arm64.
Sami
Powered by blists - more mailing lists