From: Borislav Petkov <bp@alien8.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andi Kleen <ak@linux.intel.com>,
x86@kernel.org, hpa@zytor.com, eranian@google.com,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl
Subject: Re: [PATCH 1/2] x86: Track minimum microcode revision globally v2
Date: Wed, 13 Jun 2012 08:55:25 +0200 [thread overview]
Message-ID: <20120613065525.GA12814@liondog.tnic> (raw)
In-Reply-To: <20120612225344.GE11413@one.firstfloor.org>
On Wed, Jun 13, 2012 at 12:53:44AM +0200, Andi Kleen wrote:
> I would consider that a BIOS bug.
Ok, but does the user need to know this? If it is of only informative
nature, he can find out each core's ucode version from /proc/cpuinfo so
why do we need to issue this at boot?
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-06-13 6:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 21:25 Andi Kleen
2012-06-12 21:25 ` [PATCH 2/2] perf/x86: check ucode before disabling PEBS on SandyBridge v3 Andi Kleen
2012-06-12 21:39 ` [PATCH 1/2] x86: Track minimum microcode revision globally v2 Borislav Petkov
2012-06-12 22:09 ` Andi Kleen
2012-06-12 22:19 ` Borislav Petkov
2012-06-12 22:53 ` Andi Kleen
2012-06-13 6:55 ` Borislav Petkov [this message]
2012-06-13 8:49 ` Peter Zijlstra
2012-06-13 14:49 ` Andi Kleen
2012-06-13 8:57 ` Peter Zijlstra
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=20120613065525.GA12814@liondog.tnic \
--to=bp@alien8.de \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=hpa@zytor.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®