Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp352733pxb; Fri, 28 Jan 2022 00:06:50 -0800 (PST) X-Google-Smtp-Source: ABdhPJy0utdJeXtGaMB9qttxHXkWnjbKNgPxstTkVO4mVnxjK1zus5y/FJ1dYykuJFUXtseeo2+X X-Received: by 2002:a17:906:3c56:: with SMTP id i22mr5626751ejg.415.1643357210565; Fri, 28 Jan 2022 00:06:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643357210; cv=none; d=google.com; s=arc-20160816; b=idWS3IpHagL3LqqJvDR/t7DvGScoI0Hx0K+HJMLEvWDTgaSkG9mnwAeYpz3QJu/eKa EdFiI/oeVNeXN44nQZ13t2+UoWbpiQe2mZH4e9QjvVTyar2VVG0SAKvCUdVCUVDWp37x 7at7RPQh7WKduHJvfRREMKZ0EV9NDOWZpewICckWnVZIyYaO+Z0Ia7NBnLOCnWGh6J3g bf9EDnQudzxsD0qKCL9tHP29nMMd6BA4sAZTK8ucVCY2pICldPo7z+cRbwJVwVgbP95A 5/m0cEe5a7HR0XO2M3GYXIeMV3tIFDm7BthFTaKLO90qPMXzyTh/IY6tlSFE7Kmp7vQ+ tUlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=MM3mlkgPNz3VRanbe6Q2yF8PwWWepcvoMK3GfxhgWQs=; b=IbjCPIeVOqLpjg+k8EZXOa6nVhVEEfH66mKkmVFbCudiJZflymjjyy5fTHceARehEC qpc8PRMxGfeuegyUYHiqFlBIErgRX64Ne4hcIp3pgkYIxK5DwEe7LC6GfrDJEaZPrh8e d8hymZh7UlMLQKieJJOliAZNgqImyUUfuotKh01Zllpji3sCMbCUZdAXL7wtG55/j4fS t22H9V/mOXngcUHW1ncbfc2O/bbQnbmg+mGNwTMeYoBqyWt9DDEGi6coF2RTM3HbtBYC cBe/VNpm8satCmx4uOTjf3j0+VhHr77lIOwy+xfpdqX7Y+mqRkLkjFvGUp328JdYn1tm 2YFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm2 header.b=P2YQ8gi+; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=k5s14h60; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cq4si2835878edb.595.2022.01.28.00.06.26; Fri, 28 Jan 2022 00:06:50 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm2 header.b=P2YQ8gi+; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=k5s14h60; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238028AbiA0Pgg (ORCPT + 99 others); Thu, 27 Jan 2022 10:36:36 -0500 Received: from wnew1-smtp.messagingengine.com ([64.147.123.26]:41591 "EHLO wnew1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237659AbiA0Pgf (ORCPT ); Thu, 27 Jan 2022 10:36:35 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.west.internal (Postfix) with ESMTP id 602D22B000EF; Thu, 27 Jan 2022 10:36:33 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 27 Jan 2022 10:36:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; bh=MM3mlkgPNz3VRanbe6Q2yF8PwWWepcvoMK3Gfx hgWQs=; b=P2YQ8gi+Lu9QFkGb5ntAXFjxYQyHkFcM9oLOuKOo3uYqntdqgXi9+w NRAHIcF3yeMynrermh13Zfu+wxYNYQ6GbI1tmPrI7UxS8W6eKx7akBmr7FqqXOe3 cPaFA+WocVMqf+3n8/nU1MKO6di/QioQ11RaP1e7JIJ2n4vuDhlQ3ZIJxvYe0PtG ywUNjwb2+M2AChhmiQZQe8AZeQh0MFCgjBTygURKRpX3b8nlKjj7ZktSYHBOG2oT pL4Kp6oVTlOqlVEcuRwg9TRMLrdZvZfaoJT4KjSSoLyFL3j6sV8bdOEG/KpO2ai2 tDLIQkHFbQeZHOdkeAa3OAnQ3SgUMJzQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=MM3mlkgPNz3VRanbe 6Q2yF8PwWWepcvoMK3GfxhgWQs=; b=k5s14h60VAO9d7lRux0hmyLpKCkELrhQr 0feRYcYkI8gSlWOUh5z5wg4MBcVdoRlgQ8xKWQdsvZ79swSemahTM1Zx2y7Icw6p LbgCVFEJbvbbhJmCM4/ra7/s+AVy0l0aP5UqMpPKAtdKhytoq0XpYg+ErBw+Y3vQ MwGyVXMs/bfibdKOT5aoIbJ7TPsPtp/nmgda40BoxFhjlT3xk3xJ3msg9x4Bmkvp Ku46z6O3dw2RZ2ZwIc5G+lELDVWgkvy/BMo3hxyXaNIgpDuYb1y+VmkBijTftYjr N1Np2u4RUxadnAQjBd+Pn+bPahB8pJRgOsLoWtJxfEFoGcIsYrXLQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrfeefgdejkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghgucfm jfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepveeuheejgf ffgfeivddukedvkedtleelleeghfeljeeiueeggeevueduudekvdetnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 27 Jan 2022 10:36:32 -0500 (EST) Date: Thu, 27 Jan 2022 16:36:30 +0100 From: Greg KH To: Anders Roxell Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org, Stefan Agner , Arnd Bergmann , Russell King Subject: Re: [4.9 PATCH] ARM: 8800/1: use choice for kernel unwinders Message-ID: References: <20220125134148.3390940-1-anders.roxell@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220125134148.3390940-1-anders.roxell@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 25, 2022 at 02:41:48PM +0100, Anders Roxell wrote: > From: Stefan Agner > > commit f9b58e8c7d031b0daa5c9a9ee27f5a4028ba53ac upstream. > > While in theory multiple unwinders could be compiled in, it does > not make sense in practise. Use a choice to make the unwinder > selection mutually exclusive and mandatory. > > Already before this commit it has not been possible to deselect > FRAME_POINTER. Remove the obsolete comment. > > Furthermore, to produce a meaningful backtrace with FRAME_POINTER > enabled the kernel needs a specific function prologue: > mov ip, sp > stmfd sp!, {fp, ip, lr, pc} > sub fp, ip, #4 > > To get to the required prologue gcc uses apcs and no-sched-prolog. > This compiler options are not available on clang, and clang is not > able to generate the required prologue. Make the FRAME_POINTER > config symbol depending on !clang. > > Suggested-by: Arnd Bergmann > Signed-off-by: Stefan Agner > Reviewed-by: Arnd Bergmann > Signed-off-by: Russell King > Signed-off-by: Anders Roxell > --- > arch/arm/Kconfig.debug | 44 +++++++++++++++++++++++++++--------------- > lib/Kconfig.debug | 6 +++--- > 2 files changed, 31 insertions(+), 19 deletions(-) Now queued up, thanks. greg k-h