[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee1620d5-9650-5bfa-c458-fa2d051522b1@metux.net>
Date: Thu, 25 Apr 2019 12:46:18 +0200
From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To: "Li, Aubrey" <aubrey.li@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>
Cc: 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 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
#2: still leave it selectable to the user, so somebody who doesn't need
it, can just disable it.
(I, personally, tend to disable everything I don't need)
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists