From: Ingo Molnar <mingo@elte.hu>
To: Andreas Herrmann <herrmann.der.user@googlemail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH 2/2] x86, amd-ucode: Remove needless log messages
Date: Sun, 8 Nov 2009 15:57:48 +0100 [thread overview]
Message-ID: <20091108145748.GB12290@elte.hu> (raw)
In-Reply-To: <20091029134742.GD30802@alberich.amd.com>
* Andreas Herrmann <herrmann.der.user@googlemail.com> wrote:
>
> Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
> ---
> arch/x86/kernel/microcode_amd.c | 9 +--------
> 1 files changed, 1 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kernel/microcode_amd.c b/arch/x86/kernel/microcode_amd.c
> index f4c538b..c043534 100644
> --- a/arch/x86/kernel/microcode_amd.c
> +++ b/arch/x86/kernel/microcode_amd.c
> @@ -185,9 +181,6 @@ get_next_ucode(const u8 *buf, unsigned int size, unsigned int *mc_size)
>
> total_size = (unsigned long) (section_hdr[4] + (section_hdr[5] << 8));
>
> - printk(KERN_DEBUG "microcode: size %u, total_size %u\n",
> - size, total_size);
> -
we should remove this one indeed.
> @@ -109,12 +109,8 @@ static int get_matching_microcode(int cpu, void *mc, int rev)
> return 0;
> }
>
> - if (mc_header->processor_rev_id != equiv_cpu_id) {
> - printk(KERN_ERR "microcode: CPU%d: patch mismatch "
> - "(processor_rev_id: %x, equiv_cpu_id: %x)\n",
> - cpu, mc_header->processor_rev_id, equiv_cpu_id);
> + if (mc_header->processor_rev_id != equiv_cpu_id)
> return 0;
> - }
>
> /* ucode might be chipset specific -- currently we don't support this */
> if (mc_header->nb_dev_id || mc_header->sb_dev_id) {
but why remove this one? Someone tries to load a mismatching microcode
file, isnt that some sort of bug in user-space? (Which ought to find out
whether it has anything for the CPU at hand, and only attempt it if it's
matching - or so.)
maybe it's not a KERN_ERR but KERN_INFO, but still.
Ingo
next prev parent reply other threads:[~2009-11-08 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 13:45 [PATCH 1/2] x86, amd-ucode: Check UCODE_MAGIC before loading the container file Andreas Herrmann
2009-10-29 13:47 ` [PATCH 2/2] x86, amd-ucode: Remove needless log messages Andreas Herrmann
2009-11-08 14:57 ` Ingo Molnar [this message]
2009-11-09 13:35 ` Andreas Herrmann
2009-11-10 5:15 ` [tip:x86/microcode] " tip-bot for Andreas Herrmann
2009-11-08 12:04 ` [PATCH 1/2] x86, amd-ucode: Check UCODE_MAGIC before loading the container file Ingo Molnar
2009-11-08 14:10 ` Borislav Petkov
2009-11-08 14:55 ` Ingo Molnar
2009-11-10 4:51 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
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=20091108145748.GB12290@elte.hu \
--to=mingo@elte.hu \
--cc=borislav.petkov@amd.com \
--cc=herrmann.der.user@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®