[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230419161713.qtmnnt5n64c2vvmm@treble>
Date: Wed, 19 Apr 2023 09:17:13 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: David Laight <David.Laight@...LAB.COM>
Cc: 'Chen Zhongjin' <chenzhongjin@...wei.com>,
Dave Hansen <dave.hansen@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"akpm@...ux-foudation.org" <akpm@...ux-foudation.org>,
"ben-linux@...ff.org" <ben-linux@...ff.org>,
"wuchi.zero@...il.com" <wuchi.zero@...il.com>
Subject: Re: [PATCH 1/2] x86: profiling: remove lock functions hack for
!FRAME_POINTER
On Wed, Apr 12, 2023 at 10:01:18AM +0000, David Laight wrote:
> From: Chen Zhongjin
> > Sent: 12 April 2023 08:02
> ...
> > > 4. !CONFIG_FRAME_POINTER is probably even more rare today than it was in
> > > 2006
> >
> > No. !CONFIG_FRAME_POINTER is more common today because of UNWINDER_ORC.
> > And that is why the bug is triggered more frequently.
>
> CONFIG_FRAME_POINTER is pretty much required (on x86-64)
> for the user copy checks that are enabled in distro kernels.
CONFIG_FRAME_POINTER is pretty much deprecated. The only distro still
using it (that I know of) is Ubuntu.
--
Josh
Powered by blists - more mailing lists