From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>, 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 13:52:14 -0700 [thread overview]
Message-ID: <4FD7ABFE.6090801@zytor.com> (raw)
In-Reply-To: <20120612204917.GA26817@liondog.tnic>
On 06/12/2012 01:49 PM, Borislav Petkov wrote:
>
> What do we need that for? Mixed-ucode versions?
>
Different CPUs in a multisocket system may have different compatible
ucode versions. 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.
-hpa
next prev parent reply other threads:[~2012-06-12 20:52 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 [this message]
2012-06-12 20:59 ` Borislav Petkov
2012-06-12 21:03 ` Andi Kleen
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=4FD7ABFE.6090801@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=eranian@google.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