From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935654AbdADLt0 (ORCPT ); Wed, 4 Jan 2017 06:49:26 -0500 Received: from foss.arm.com ([217.140.101.70]:49104 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934392AbdADLtW (ORCPT ); Wed, 4 Jan 2017 06:49:22 -0500 Date: Wed, 4 Jan 2017 11:49:21 +0000 From: Will Deacon To: Florian Fainelli Cc: Markus Mayer , Markus Mayer , Catalin Marinas , Linux Kernel Mailing List , ARM Kernel Mailing List Subject: Re: [PATCH] arm64: errata: Check for --fix-cortex-a53-843419 and --fix-cortex-a53 Message-ID: <20170104114920.GB18193@arm.com> References: <20161031194414.61287-1-code@mmayer.net> <20161102210331.GJ22791@arm.com> <20161102212747.GL22791@arm.com> <2d72cbbb-df03-267c-53b0-e3083a746175@gmail.com> <20161103141559.GQ22791@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Florian, On Wed, Dec 28, 2016 at 12:17:23PM -0800, Florian Fainelli wrote: > On 11/03/2016 10:20 AM, Florian Fainelli wrote: > > On 11/03/2016 07:16 AM, Will Deacon wrote: > >> If you can't change toolchain and you want this worked around, why can't you > >> either build gold with it enabled by default, or pass the extra flag on the > >> command line to the kernel build system? > > > > Because that creates a distribution problem and now we have to document > > this for people who want to build a kernel on their own, without > > necessarily understanding if this is something they might need, or why > > this is needed, and why the kernel is not taking care of that on its > > own? So yes, this comes down to who is responsible for what, in that > > case the kernel's Makefile is the best place where to put such knowledge > > as to which workaround needs to be enabled by the linker and it > > simplifies things a lot for people. > > Was this convincing enough for Catalin to pick Markus' patch or does > that mean this patch needs to remain out of tree for us because of using > a slightly older toolchain? I thought more about this last night, and there are two questions that might sway me: 1. How prevalent is the binary toolchain with this issue? Is it, for example, shipping as part of a publicly available LTS distribution? I know you quoted some Linaro build, but I can't actually find those binaries on their website. 2. Could we extend the Makefile magic to detect that, not only is --fix-cortex-a53-843419 unsupported, but also that the linker is in fact gold? Will