From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] x86/microcode: Unify early reporting
Date: Wed, 15 Nov 2023 22:02:10 +0100 [thread overview]
Message-ID: <20231115210212.9981-1-bp@alien8.de> (raw)
From: "Borislav Petkov (AMD)" <bp@alien8.de>
Hi,
this has been a pet peeve of mine for a while now and Linus prompted me
to finally do it.
So, this reworks the early microcode revision reporting on both sides of
the loader and unifies them into issuing only two lines max, for
example:
microcode: Current revision: 0x0a201025
microcode: Updated early from: 0x0a201016
The per-thread microcode revisions are in /proc/cpuinfo anyway so
grepping that is what people who are really interested, should do while
dmesg remains *not* flooded with the same revision number over and over
again.
Thx.
Borislav Petkov (AMD) (2):
x86/microcode: Remove the driver announcement and version
x86/microcode: Rework early revisions reporting
arch/x86/kernel/cpu/microcode/amd.c | 39 +++++++-----------------
arch/x86/kernel/cpu/microcode/core.c | 16 ++++++----
arch/x86/kernel/cpu/microcode/intel.c | 17 +++++------
arch/x86/kernel/cpu/microcode/internal.h | 14 ++++++---
4 files changed, 38 insertions(+), 48 deletions(-)
base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
--
2.42.0.rc0.25.ga82fb66fed25
next reply other threads:[~2023-11-15 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 21:02 Borislav Petkov [this message]
2023-11-15 21:02 ` [PATCH 1/2] x86/microcode: Remove the driver announcement and version Borislav Petkov
2023-11-21 15:42 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov (AMD)
2023-11-15 21:02 ` [PATCH 2/2] x86/microcode: Rework early revisions reporting Borislav Petkov
2023-11-30 18:34 ` Ashok Raj
2023-12-01 16:39 ` Borislav Petkov
2023-12-01 20:33 ` Ashok Raj
2023-12-01 20:41 ` Borislav Petkov
2023-12-01 21:32 ` Ashok Raj
2023-12-02 16:38 ` Borislav Petkov
2023-12-02 23:35 ` Ashok Raj
2023-12-03 11:15 ` [tip: x86/microcode] x86/microcode/intel: Set new revision only after a successful update tip-bot2 for Borislav Petkov (AMD)
2023-11-30 18:46 ` [PATCH 2/2] x86/microcode: Rework early revisions reporting Ashok Raj
2023-12-01 18:37 ` [tip: x86/microcode] x86/microcode/intel: Remove redundant microcode late updated message tip-bot2 for Ashok Raj
2023-11-21 15:05 ` [PATCH 0/2] x86/microcode: Unify early reporting Thomas Gleixner
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=20231115210212.9981-1-bp@alien8.de \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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.