From: "David Schwartz" <davids@webmaster.com>
To: "Justin Piszcz" <jpiszcz@hotmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Linux Kernel Microcode Question
Date: Thu, 18 Mar 2004 09:13:37 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMENKLCAA.davids@webmaster.com> (raw)
In-Reply-To: <20040318165952.GA24328@redhat.com>
> > Is it worth it?
> In most cases, yes. It's zero cost. You don't waste RAM, as the
> microcode gets loaded into small RAM areas on the CPU that are
> otherwise unused.
It is at least theoeretically possible that a microcode update might cause
an operation that's normally done very quickly (in dedicated hardware) to be
done by a slower path (microcode operations) to fix a bug in the dedicated
hardware that is very obscure and very unlikely to ever bother you. However,
I have never heard of even a single confirmed instance where this happened.
DS
next prev parent reply other threads:[~2004-03-18 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 16:40 Justin Piszcz
2004-03-18 16:59 ` Dave Jones
2004-03-18 17:13 ` David Schwartz [this message]
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=MDEHLPKNGKAHNMBLJOLKMENKLCAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=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
Powered by JetHome