[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1904251249200.1960@nanos.tec.linutronix.de>
Date: Thu, 25 Apr 2019 12:50:49 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
cc: "Li, Aubrey" <aubrey.li@...ux.intel.com>, mingo@...hat.com,
peterz@...radead.org, hpa@...or.com, ak@...ux.intel.com,
tim.c.chen@...ux.intel.com, dave.hansen@...el.com,
arjan@...ux.intel.com, adobriyan@...il.com,
akpm@...ux-foundation.org, aubrey.li@...el.com,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH v17 1/3] proc: add /proc/<pid>/arch_status
On Thu, 25 Apr 2019, Enrico Weigelt, metux IT consult wrote:
> On 25.04.19 12:42, Li, Aubrey wrote:
> >
> > Yep, I'll make it disabled by default and not switchable and let arch select it.
> >
>
> That's not quite what I've suggested. Instead:
>
> #1: make the switch depend on the arch's that support it
No. That's what select is for.
> #2: still leave it selectable to the user, so somebody who doesn't need
> it, can just disable it.
Well, the number of knobs is exploding over time and the number of people
actually tweaking them is close to 0. So no, we don't want to have the
extra tunable for everything and the world.
Thanks,
tglx
Powered by blists - more mailing lists