From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Sean Christopherson <seanjc@google.com>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [RFC PATCH] x86/cpufeatures: Flip the /proc/cpuinfo appearance logic
Date: Tue, 18 Jun 2024 08:46:59 -0700 [thread overview]
Message-ID: <9e5fed54-d1ee-4001-9835-e9aa7b4a3ce0@intel.com> (raw)
In-Reply-To: <20240618113840.24163-1-bp@kernel.org>
On 6/18/24 04:38, Borislav Petkov wrote:
> Flip the logic to make it explicit: an explicit "<name>" in the comment
> adds the flag to /proc/cpuinfo and otherwise not, by default.
This makes a lot of sense. Historically, it seems like most things were
exposed in /proc/cpuinfo, but that trend has reversed and it's becoming
the exception rather than the rule.
Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
next prev parent reply other threads:[~2024-06-18 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 11:38 [RFC PATCH] x86/cpufeatures: Flip the /proc/cpuinfo appearance logic Borislav Petkov
2024-06-18 14:06 ` Sean Christopherson
2024-06-18 18:36 ` Borislav Petkov
2024-06-18 15:46 ` Dave Hansen [this message]
2024-06-19 8:11 ` H. Peter Anvin
2024-06-20 18:40 ` Borislav Petkov
2024-06-21 10:31 ` [tip: x86/cpu] " tip-bot2 for Borislav Petkov (AMD)
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=9e5fed54-d1ee-4001-9835-e9aa7b4a3ce0@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox