[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dfd39410-7b02-c478-7228-820ab737d4a1@intel.com>
Date: Fri, 21 Dec 2018 07:19:06 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Borislav Petkov <bp@...en8.de>,
"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 12/21/18 5:04 AM, Borislav Petkov wrote:
>
> $ 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 ...
I don't always look at these through the shell. I got a screenshot the
other day, or someone pasted the flags into a spreadsheet.
/proc/cpuinfo is supposed to be human-readable. But, the flags field,
as it stands, is not. You've further proved my point by having to
machine post-process it to make it usable by humans. :)
Powered by blists - more mailing lists