From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jia Zhang <qianyue.zj@alibaba-inc.com>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>
Subject: Re: [PATCH] x86/cpu: sort cpuinfo flags
Date: Fri, 21 Dec 2018 07:19:06 -0800 [thread overview]
Message-ID: <dfd39410-7b02-c478-7228-820ab737d4a1@intel.com> (raw)
In-Reply-To: <20181221130403.GD1325@zn.tnic>
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. :)
next prev parent reply other threads:[~2018-12-21 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 19:50 [PATCH] x86/cpu: sort cpuinfo flags Dave Hansen
2018-12-20 12:02 ` Kirill A. Shutemov
2018-12-20 16:04 ` Borislav Petkov
2018-12-21 12:40 ` Kirill A. Shutemov
2018-12-21 13:04 ` Borislav Petkov
2018-12-21 13:19 ` Kirill A. Shutemov
2018-12-21 13:26 ` Borislav Petkov
2018-12-21 15:19 ` Dave Hansen [this message]
2018-12-21 16:12 ` Borislav Petkov
2018-12-20 12:07 ` Kirill A. Shutemov
2018-12-21 9:37 ` kbuild test robot
2018-12-22 7:17 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfd39410-7b02-c478-7228-820ab737d4a1@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=garsilva@embeddedor.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qianyue.zj@alibaba-inc.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.