[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160928065602.GS2794@worktop>
Date: Wed, 28 Sep 2016 08:56:02 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc: Kim Phillips <kim.phillips@....com>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Petr Mladek <pmladek@...e.com>,
Kees Cook <keescook@...omium.org>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
linux-kernel@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-snps-arc@...ts.infradead.org,
Thomas Garnier <thgarnie@...gle.com>
Subject: Re: [PATCH] perf: remove orphan DEBUG_PERF_USE_VMALLOC
On Tue, Sep 27, 2016 at 09:51:35AM -0700, Vineet Gupta wrote:
> On 09/27/2016 09:37 AM, Kim Phillips wrote:
> > On Tue, 27 Sep 2016 07:53:56 -0700
> > Vineet Gupta <Vineet.Gupta1@...opsys.com> wrote:
> >
> >> > This doesn't seem to be used anywhere
> > I thought so too, until I got this response for an equivalent patch:
> >
> > https://lkml.org/lkml/2016/8/31/53
>
> So this is some sort of "developer shortcut" to quickly enable 2 options with one
> option. Purpose seems dubious to me ! It would still be possible to enable vmalloc
> backed mmap on x86 by simply enabling that option from Kconfig.
PERF_USE_VMALLOC is not a user selectable option. Also
DEBUG_PERF_USE_VMALLOC clearly indicates its a _DEBUG_ option. Heck,
even the help text says what its for.
Powered by blists - more mailing lists