public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Herrmann <herrmann.der.user@googlemail.com>
To: dimm <dmitry.adamushko@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	Mike Travis <travis@sgi.com>,
	Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <borislav.petkov@amd.com>,
	Andreas Mohr <andi@lisas.de>, Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ RFC, PATCH - 1/2 ] x86-microcode: refactor microcode output messages
Date: Mon, 2 Nov 2009 17:46:21 +0100	[thread overview]
Message-ID: <20091102164621.GF30802@alberich.amd.com> (raw)
In-Reply-To: <1257114179.6833.47.camel@dimm>

On Sun, Nov 01, 2009 at 11:22:59PM +0100, dimm wrote:
> 
> Hi,
> 
> 
> this is in response to Mike's patch "Limit the number of microcode
> messages".
> 
> What's about the following (yet preliminary and not thoroughly tested)
> approach?

Hmm, patch-1 doesn't apply:

 patching file arch/x86/include/asm/microcode.h
 patching file arch/x86/kernel/microcode_amd.c
 Hunk #1 succeeded at 152 (offset -4 lines).
 Hunk #2 succeeded at 240 (offset -7 lines).
 patch: **** malformed patch at line 99: size_t size)


> patch-1:
> 
> simplify 'struct ucode_cpu_info' and related operational logic.
> 
> 
> patch-2: 
> 
> reduce a number of similar 'microcode version' messages by printing a
> single message for all cpus with equal microcode version, like:

Would be useful on systems with many cores.

On AMD multi-socket systems often you have the same CPU revisions and
thus you'd like to have similar ucode on all cores. Hence there is a
high chance that your code would reduce the amount of microcode log
messages during boot.

I'd like to test it but would need patches that do apply ...


Thanks,
Andreas

  parent reply	other threads:[~2009-11-02 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 22:22 [ RFC, PATCH - 1/2 ] x86-microcode: refactor microcode output messages dimm
2009-11-01 22:25 ` [ RFC, PATCH - 2/2 " dimm
2009-11-02 16:46 ` Andreas Herrmann [this message]
2009-11-02 17:17   ` [ RFC, PATCH - 1/2 " Mike Travis
2009-11-02 17:19   ` Dmitry Adamushko

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=20091102164621.GF30802@alberich.amd.com \
    --to=herrmann.der.user@googlemail.com \
    --cc=andi@lisas.de \
    --cc=borislav.petkov@amd.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=tigran@aivazian.fsnet.co.uk \
    --cc=travis@sgi.com \
    /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