From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Andi Kleen <andi@firstfloor.org>
Cc: x86@kernel.org, elliott@hpe.com, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86/microcode/intel: Quieten down microcode updates on large systems
Date: Thu, 9 Jun 2016 20:58:36 -0300 [thread overview]
Message-ID: <20160609235836.GC30888@khazad-dum.debian.net> (raw)
In-Reply-To: <20160609134141.5981-1-andi@firstfloor.org>
On Thu, 09 Jun 2016, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> On large systems the microcode driver is very noisy, because it prints
> a line for each CPU. The lines are redundant because because usually
> all CPUs are updated to the same microcode revision.
>
> All other subsystems have been patched previously to not print
> a line for each CPU. Only the microcode driver is left.
>
> Only print an microcode revision update when something changed. This results
> in typically only a single line being printed.
>
> v2: Change message to "One or more CPUs"
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
Thanks, for WLIW,
Reviewed-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> ---
> arch/x86/kernel/cpu/microcode/intel.c | 25 ++++++++++++++++++-------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/microcode/intel.c b/arch/x86/kernel/cpu/microcode/intel.c
> index cbb3cf0..54f5f6c 100644
> --- a/arch/x86/kernel/cpu/microcode/intel.c
> +++ b/arch/x86/kernel/cpu/microcode/intel.c
> @@ -794,6 +794,7 @@ void reload_ucode_intel(void)
>
> static int collect_cpu_info(int cpu_num, struct cpu_signature *csig)
> {
> + static struct cpu_signature prev;
> struct cpuinfo_x86 *c = &cpu_data(cpu_num);
> unsigned int val[2];
>
> @@ -808,8 +809,14 @@ static int collect_cpu_info(int cpu_num, struct cpu_signature *csig)
> }
>
> csig->rev = c->microcode;
> - pr_info("CPU%d sig=0x%x, pf=0x%x, revision=0x%x\n",
> - cpu_num, csig->sig, csig->pf, csig->rev);
> +
> + /* No extra locking on prev, races are harmless. */
> + if (csig->sig != prev.sig || csig->pf != prev.pf ||
> + csig->rev != prev.rev) {
> + pr_info("One or more CPUs sig=0x%x, pf=0x%x, revision=0x%x\n",
> + csig->sig, csig->pf, csig->rev);
> + prev = *csig;
> + }
>
> return 0;
> }
> @@ -838,6 +845,7 @@ static int apply_microcode_intel(int cpu)
> struct ucode_cpu_info *uci;
> struct cpuinfo_x86 *c;
> unsigned int val[2];
> + static int prev_rev;
>
> /* We should bind the task to the CPU */
> if (WARN_ON(raw_smp_processor_id() != cpu))
> @@ -872,11 +880,14 @@ static int apply_microcode_intel(int cpu)
> return -1;
> }
>
> - pr_info("CPU%d updated to revision 0x%x, date = %04x-%02x-%02x\n",
> - cpu, val[1],
> - mc->hdr.date & 0xffff,
> - mc->hdr.date >> 24,
> - (mc->hdr.date >> 16) & 0xff);
> + if (val[1] != prev_rev) {
> + pr_info("One or more CPUs updated to revision 0x%x, date = %04x-%02x-%02x\n",
> + val[1],
> + mc->hdr.date & 0xffff,
> + mc->hdr.date >> 24,
> + (mc->hdr.date >> 16) & 0xff);
> + prev_rev = val[1];
> + }
>
> c = &cpu_data(cpu);
>
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2016-06-09 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 13:41 Andi Kleen
2016-06-09 23:58 ` Henrique de Moraes Holschuh [this message]
2016-06-10 9:54 ` Borislav Petkov
2016-06-14 11:25 ` [tip:x86/microcode] x86/microcode/intel: Do not issue microcode updates messages on each CPU tip-bot for Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2016-05-31 21:22 [PATCH] x86/microcode/intel: Quieten down microcode updates on large systems Andi Kleen
2016-06-09 4:34 ` Elliott, Robert (Persistent Memory)
2016-06-09 15:47 ` Henrique de Moraes Holschuh
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=20160609235836.GC30888@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=elliott@hpe.com \
--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 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®