From: Andreas Herrmann <herrmann.der.user@googlemail.com>
To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, dimm <dmitry.adamushko@gmail.com>
Subject: [PATCH 0/3] x86, ucode-amd: trim verbosity
Date: Tue, 10 Nov 2009 12:06:01 +0100 [thread overview]
Message-ID: <20091110110601.GG30802@alberich.amd.com> (raw)
Following patches make log messages of microcode_amd more terse.
Especially in conjunction with Dmitry's planned changes to summarize
patch level information this will help to trim messages to the
necessary minimum on systems with many CPUs.
Example (without patch 1 and 2) of a 48 CPU system:
microcode: CPU0: patch_level=0x10000b5
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: CPU0: cpu revision not listed in equivalent cpu table
microcode: CPU0: cpu revision not listed in equivalent cpu table
microcode: CPU1: patch_level=0x10000b5
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: CPU1: cpu revision not listed in equivalent cpu table
microcode: CPU1: cpu revision not listed in equivalent cpu table
...
microcode: CPU46: patch_level=0x10000b5
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: CPU46: cpu revision not listed in equivalent cpu table
microcode: CPU46: cpu revision not listed in equivalent cpu table
microcode: CPU47: patch_level=0x10000b5
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: CPU47: cpu revision not listed in equivalent cpu table
microcode: CPU47: cpu revision not listed in equivalent cpu table
Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
This is a lot of unnecessary noise. With patches 1 and 2 applied this
is shortened to:
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: CPU0: patch_level=0x10000b5
microcode: CPU1: patch_level=0x10000b5
...
microcode: CPU46: patch_level=0x10000b5
microcode: CPU47: patch_level=0x10000b5
Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
And with Dmitry's patches this will be trimmed down even further.
Note: Patch 3 is just a conversion from printk to pr_ macros.
Patches are against tip/master.
Please apply.
Thanks,
Andreas
next reply other threads:[~2009-11-10 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 11:06 Andreas Herrmann [this message]
2009-11-10 11:07 ` [PATCH 1/3] x86, ucode-amd: Load ucode-patches once and not separately fo each CPU Andreas Herrmann
2009-11-10 12:02 ` Dmitry Adamushko
2009-11-11 7:51 ` Clemens Ladisch
2009-11-11 11:27 ` Andreas Herrmann
2009-11-12 15:05 ` Andreas Herrmann
2009-11-10 13:21 ` [tip:x86/microcode] x86: ucode-amd: Load ucode-patches once and not separately of " tip-bot for Andreas Herrmann
2009-11-10 11:08 ` [PATCH 2/3] x86, ucode-amd: Don't warn when no ucode is available for a CPU revision Andreas Herrmann
2009-11-10 13:22 ` [tip:x86/microcode] x86: " tip-bot for Andreas Herrmann
2009-11-10 11:09 ` [PATCH 3/3] x86, ucode-amd: printk(KERN_* to pr_* conversion Andreas Herrmann
2009-11-10 13:22 ` [tip:x86/microcode] x86: ucode-amd: Convert printk(KERN_*...) to pr_*(...) tip-bot for Andreas Herrmann
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=20091110110601.GG30802@alberich.amd.com \
--to=herrmann.der.user@googlemail.com \
--cc=dmitry.adamushko@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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