From: Andi Kleen <andi@firstfloor.org>
To: Borislav Petkov <bp@alien8.de>, Andi Kleen <ak@linux.intel.com>,
Andi Kleen <andi@firstfloor.org>,
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 00:53:44 +0200 [thread overview]
Message-ID: <20120612225344.GE11413@one.firstfloor.org> (raw)
In-Reply-To: <20120612221931.GA4376@liondog.tnic>
On Wed, Jun 13, 2012 at 12:19:31AM +0200, Borislav Petkov wrote:
> On Tue, Jun 12, 2012 at 03:09:25PM -0700, Andi Kleen wrote:
> >
> > >Ok, is it only me or is this boot_min_microcode superfluous?
> > >IOW, you can only use boot_cpu_data.microcode instead and drop
> > >boot_min_microcode.
> >
> > boot_cpu_data.microcode contains a copy of the original microcode,
> > so we couldn't detect the boot cpu case. In theory could hard code
> > CPU #0 is boot cpu or so,
> > but I prefer to track it with the separate variable.
>
> Ok, this begs the next question then: why do we need to say that some AP
> has a lower ucode version than the BSP?
I would consider that a BIOS bug.
-Andi
next prev parent reply other threads:[~2012-06-12 22:53 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 [this message]
2012-06-13 6:55 ` Borislav Petkov
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=20120612225344.GE11413@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome