From: "Justin Piszcz" <jpiszcz@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Linux Kernel Microcode Question
Date: Thu, 18 Mar 2004 16:40:49 +0000 [thread overview]
Message-ID: <Law10-F95ihL5C2Skqk00028182@hotmail.com> (raw)
The URL: http://www.urbanmyth.org/microcode/
The microcode_ctl utility is a companion to the IA32 microcode driver
written by Tigran Aivazian <tigran@veritas.com>. The utility has two uses:
* it decodes and sends new microcode to the kernel driver to be uploaded
to Intel IA32 processors. (Pentium Pro, PII, PIII, Pentium 4, Celeron, Xeon
etc - all P6 and above, which does NOT include pentium classics)
* it signals the kernel driver to release any buffers it may hold
The microcode update is volatile and needs to be uploaded on each system
boot i.e. it doesn't reflash your cpu permanently, reboot and it reverts
back to the old microcode.
My question is, what are the advantages vs disadvantages in updating your
CPU's microcode?
Is it worth it?
Does it matter what type of Intel CPU you have?
Do some CPU's benefit more than others for microcode updates?
I know RedHat distributions usually do this by default, but others do not.
Can anyone explain reasons to or not to update the CPU microcode?
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now!
http://clk.atdmt.com/AVE/go/onm00200415ave/direct/01/
next reply other threads:[~2004-03-18 16:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 16:40 Justin Piszcz [this message]
2004-03-18 16:59 ` Dave Jones
2004-03-18 17:13 ` David Schwartz
2004-03-19 17:27 ` Tigran Aivazian
2004-03-19 23:16 ` David Schwartz
2004-03-22 11:55 ` Tigran Aivazian
2004-03-22 15:51 ` Timothy Miller
2004-03-22 15:40 ` Tigran Aivazian
2004-03-22 16:19 ` Timothy Miller
2004-03-22 19:14 ` David Schwartz
2004-03-22 20:58 ` John Bradford
2004-03-22 16:13 ` Richard B. Johnson
2004-03-22 16:51 ` Timothy Miller
2004-03-22 17:14 ` Richard B. Johnson
2004-03-18 16:59 ` Richard B. Johnson
2004-03-18 17:07 ` Robert Love
2004-03-19 0:16 ` Bill Davidsen
2004-03-19 12:56 ` Richard B. Johnson
2004-03-18 22:20 ` Tigran Aivazian
2004-03-18 17:19 Nakajima, Jun
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=Law10-F95ihL5C2Skqk00028182@hotmail.com \
--to=jpiszcz@hotmail.com \
--cc=linux-kernel@vger.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®