From: "Giacomo A. Catenazzi" <cate@pixelized.ch>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Ammar T. Al-Sayegh" <ammar@kunet.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/rmap.c:483!
Date: Mon, 28 Feb 2005 11:43:10 +0100 [thread overview]
Message-ID: <4222F5BE.7000301@pixelized.ch> (raw)
In-Reply-To: <1109237429.6530.23.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>>but what what's the
>>penalty of preventing microcode from loading? a performance
>>hit?
>
>
> not even that; in theory a few cpu bugs may have been fixed. Nobody
> really knows since there's no changelog for the microcode..
You can see the processor bugs in intel website, i.e.:
ftp://download.intel.com/design/Xeon/specupdt/24967847.pdf
The following sentence (IMHO) meens that bug is corrected in microcode:
"Workaround: It is possible for the BIOS to contain a workaround
for this erratum."
ciao
cate
next prev parent reply other threads:[~2005-02-28 10:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 20:41 kernel BUG at mm/rmap.c:483! Ammar T. Al-Sayegh
2005-02-23 20:54 ` Arjan van de Ven
2005-02-23 21:45 ` Ammar T. Al-Sayegh
2005-02-23 22:01 ` Arjan van de Ven
2005-02-23 22:46 ` Ammar T. Al-Sayegh
2005-02-24 8:38 ` Arjan van de Ven
2005-02-24 9:25 ` Ammar T. Al-Sayegh
2005-02-24 9:30 ` Arjan van de Ven
2005-02-28 10:43 ` Giacomo A. Catenazzi [this message]
2005-02-28 11:09 ` Arjan van de Ven
2005-02-23 21:31 ` Hugh Dickins
2005-02-23 22:38 ` Ammar T. Al-Sayegh
2005-02-24 5:31 ` Hugh Dickins
2005-02-24 13:25 ` Horst von Brand
-- strict thread matches above, loose matches on Subject: below --
2005-02-23 22:05 Nick Warne
2005-02-24 12:15 ` Hugh Dickins
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=4222F5BE.7000301@pixelized.ch \
--to=cate@pixelized.ch \
--cc=ammar@kunet.com \
--cc=arjan@infradead.org \
--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