From: Andi Kleen <andi@firstfloor.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Daniel J Blueman <daniel.blueman@gmail.com>,
Shaohua Li <shaohua.li@intel.com>,
jamagallon@ono.com, tigran@aivazian.fsnet.co.uk,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: New format Intel microcode...
Date: Fri, 29 Jun 2007 01:09:14 +0200 [thread overview]
Message-ID: <20070628230914.GB14519@one.firstfloor.org> (raw)
In-Reply-To: <468434DE.103@tmr.com>
> I was mainly concerned with this being a new issue, and curious if
> Microsoft was calling an O/S bug a "microcode fix," given that the
> average Windows user doesn't know microcode from nanotech anyway. The
> non-answer from Arjan didn't answer either, and started by calling the
> report FUD, implying that Slashdot was wrong (not about this), and
> issuing so little answer and so much obfuscation that I thought he might
> be running for President. ;-)
Well you can read the Intel documentation if you want the whole story.
You can hardly expect a full introduction in the basics and then
subtle issues of TLB flushing in a quick email. You asked about opinions
and summaries and those you got.
> I'd like the microcode update,
It's called the "placebo effect" in the literature I believe.
> some people elsewhere speculate that user
> level code could effect reliability if not security.
speculate is the key word.
> I worry that an old
> 2.4 kernel would be an issue, even in kvm, if that were the case.
TLB flushing in virtualization works completely different. I doubt
it would be affected.
-Andi
next prev parent reply other threads:[~2007-06-28 23:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 23:45 New format Intel microcode Daniel J Blueman
2007-03-23 0:43 ` Shaohua Li
2007-03-23 9:43 ` Marcel Holtmann
2007-03-23 9:03 ` Arjan van de Ven
2007-03-26 8:34 ` Marcel Holtmann
2007-03-26 8:52 ` Arjan van de Ven
2007-06-26 21:42 ` Daniel J Blueman
2007-06-26 23:29 ` Andi Kleen
2007-06-28 13:53 ` Bill Davidsen
2007-06-28 14:12 ` Arjan van de Ven
2007-06-28 15:48 ` Alex Riesen
2007-06-28 17:27 ` Chuck Ebbert
2007-06-28 17:29 ` Arjan van de Ven
2007-06-28 17:54 ` Daniel J Blueman
2007-06-28 15:27 ` Andi Kleen
2007-06-28 15:44 ` Chuck Ebbert
2007-06-28 22:55 ` Bill Davidsen
2007-06-28 22:23 ` Bill Davidsen
2007-06-28 22:30 ` Arjan van de Ven
2007-06-28 23:09 ` Andi Kleen [this message]
2007-07-02 8:56 ` Alex Riesen
2007-07-02 17:18 ` Arjan van de Ven
2007-07-02 18:22 ` Alex Riesen
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=20070628230914.GB14519@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=daniel.blueman@gmail.com \
--cc=davidsen@tmr.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tigran@aivazian.fsnet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.