From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andi Kleen <andi@firstfloor.org>
Cc: x86@kernel.org, hpa@zytor.com, eranian@google.com,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] x86: Track minimum microcode revision globally v2
Date: Wed, 13 Jun 2012 10:57:39 +0200 [thread overview]
Message-ID: <1339577859.31548.127.camel@twins> (raw)
In-Reply-To: <1339536350-10463-1-git-send-email-andi@firstfloor.org>
On Tue, 2012-06-12 at 14:25 -0700, Andi Kleen wrote:
> At CPU hotplug or S3 resume time there is a short race window
> where something might run on the CPUs but before the microcode
> update notifier runs. For the current workarounds that need this
> this is acceptable and shouldn't be a problem.
I'm not convinced,.. the CPU_ONLINE notifier stuff runs pretty late, by
then its already running normal userspace.
We really should do the ucode update from CPU_STARTING.
prev parent reply other threads:[~2012-06-13 8:57 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
2012-06-13 8:49 ` Peter Zijlstra
2012-06-13 14:49 ` Andi Kleen
2012-06-13 8:57 ` Peter Zijlstra [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=1339577859.31548.127.camel@twins \
--to=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®