[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181221130403.GD1325@zn.tnic>
Date: Fri, 21 Dec 2018 14:04:03 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
linux-kernel@...r.kernel.org, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jia Zhang <qianyue.zj@...baba-inc.com>,
"Gustavo A. R. Silva" <garsilva@...eddedor.com>
Subject: Re: [PATCH] x86/cpu: sort cpuinfo flags
On Fri, Dec 21, 2018 at 03:40:37PM +0300, Kirill A. Shutemov wrote:
> But I don't see an improvement in readability of data presented to user as
> a silly idea.
Improving readability is not a silly idea and I never said that. Rather,
the cost of what you're trying to accomplish, needs to be weighed.
The final goal of this is, AFAIU, finding whether a feature flag is
there or not and you can use grep for that now, on *any* kernel.
And if you need the feature flags sorted, you can do that too:
$ grep -m 1 flags /proc/cpuinfo | tr " " "\n" | sort | xargs
and there probably is even a simpler way to do that.
Or add a shell alias for that or a small script or ...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists