From: Dave Hansen <dave.hansen@intel.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Sohil Mehta <sohil.mehta@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@alien8.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] x86/its: Warn when microcode is old
Date: Thu, 12 Jun 2025 06:31:39 -0700 [thread overview]
Message-ID: <29314698-8c7d-4088-b391-6c33c21acc84@intel.com> (raw)
In-Reply-To: <20250612131909.saj4lq7dh2gqznyc@desk>
On 6/12/25 06:19, Pawan Gupta wrote:
> On a second thought, cpu_set_bug_bits() already issues a warning, and even
> taints the kernel when old microcode is detected. So warning here seems
> redundant, and also misleading as you said. I am okay dropping this patch.
Yep, that was the whole point of X86_BUG_OLD_MICROCODE. It's one, big,
bad, scary warning so that we don't have to do it for all the individual
little bad things that happen when you have old microcode.
next prev parent reply other threads:[~2025-06-12 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 0:08 Pawan Gupta
2025-06-12 6:34 ` Sohil Mehta
2025-06-12 13:19 ` Pawan Gupta
2025-06-12 13:31 ` Dave Hansen [this message]
2025-06-12 6:58 ` Nikolay Borisov
2025-06-12 13:22 ` Pawan Gupta
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=29314698-8c7d-4088-b391-6c33c21acc84@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=sohil.mehta@intel.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
all inboxes | Powered by JetHome®