From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nathan Bryant <nbryant@optonline.net>
Cc: Bill Davidsen <davidsen@tmr.com>,
Tigran Aivazian <tigran@veritas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Latest microcode data from Intel.
Date: Fri, 10 Sep 2004 16:02:14 +0100 [thread overview]
Message-ID: <1094828533.17464.7.camel@localhost.localdomain> (raw)
In-Reply-To: <4141CCA8.30807@optonline.net>
On Gwe, 2004-09-10 at 16:47, Nathan Bryant wrote:
> Potentially stupid question, how does microcode update interact with CPU
> hotplug?
You run the microcode update sequence after a CPU is plugged in. That
might be an argument for having user space kick off application use of
hotplugged processors so that some housekeeping can run first.
In the ideal case your BIOS vendor ships you needed BIOS updates to
handle such things and in a sane format.
next prev parent reply other threads:[~2004-09-10 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 16:32 Latest microcode data from Intel Tigran Aivazian
2004-09-09 21:10 ` DaMouse
2004-09-10 15:39 ` Bill Davidsen
2004-09-10 15:46 ` Tigran Aivazian
2004-09-10 14:54 ` Alan Cox
2004-09-10 16:04 ` Tigran Aivazian
2004-09-10 16:39 ` Chris Wright
2004-09-11 21:10 ` Tigran Aivazian
2004-09-10 16:14 ` Kurt Wall
2004-09-15 15:31 ` Bill Davidsen
2004-09-15 15:43 ` Tigran Aivazian
2004-09-15 15:52 ` Dave Jones
2004-09-15 16:09 ` Bill Davidsen
2004-09-10 15:47 ` Nathan Bryant
2004-09-10 15:02 ` Alan Cox [this message]
2004-09-10 15:53 ` Tigran Aivazian
2004-09-10 16:44 ` Anton Blanchard
2004-09-10 16:53 ` Dominik Karall
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 22:21 Chris Rankin
2004-09-10 21:07 watermodem
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=1094828533.17464.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbryant@optonline.net \
--cc=tigran@veritas.com \
/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