From: Andi Kleen <andi@firstfloor.org>
To: Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, eranian@google.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] x86: Track minimum microcode revision globally
Date: Tue, 12 Jun 2012 23:03:29 +0200 [thread overview]
Message-ID: <20120612210329.GD11413@one.firstfloor.org> (raw)
In-Reply-To: <20120612205956.GB26817@liondog.tnic>
On Tue, Jun 12, 2012 at 10:59:56PM +0200, Borislav Petkov wrote:
> On Tue, Jun 12, 2012 at 01:52:14PM -0700, H. Peter Anvin wrote:
> > Different CPUs in a multisocket system may have different compatible
> > ucode versions.
>
> Ah, so you need the different ucode for the different steppings of the
> cpus on the board, right? Assuming ucode versions are incremented per
> F:M:S tuple, of course, then you can have different compatible microcode
> versions.
I believe just for different models. Different models in a single system
may be possible, but are quite unsupported. The code doesn't
handle that, but I don't really worry about that.
> > Of course, I am not even sure if it makes any sense at all to compare
> > microcode versions without qualifying them with F:M:S.
It doesn't.
But I think this model handles 99.999% of all sane configs, don't
really want to complicate it more.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2012-06-12 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 20:33 [PATCH 1/2] x86: Track minimum microcode revision globally Andi Kleen
2012-06-12 20:33 ` [PATCH 2/2] perf/x86: check ucode before disabling PEBS on SandyBridge Andi Kleen
2012-06-12 20:36 ` [PATCH 1/2] x86: Track minimum microcode revision globally H. Peter Anvin
2012-06-12 20:39 ` Andi Kleen
2012-06-12 20:49 ` Borislav Petkov
2012-06-12 20:52 ` H. Peter Anvin
2012-06-12 20:59 ` Borislav Petkov
2012-06-12 21:03 ` Andi Kleen [this message]
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=20120612210329.GD11413@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.