From: "H. Peter Anvin" <hpa@zytor.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: RFC: remove or modify check_for_bios_corruption()
Date: Wed, 25 Aug 2010 16:54:16 -0700 [thread overview]
Message-ID: <4C75AD28.8060101@zytor.com> (raw)
check_for_bios_corruption() was added to discover how many systems have
BIOSes with problems corrupting low memory. The answer really is very
simple... almost all. In fact, I have seen claims that Windows 7
doesn't use any memory below the 1 MiB point at all for this reason.
As such, I have queued up a patch in -tip to reserve the low 64K for all
BIOSes, with an option (suggested by Andrew) to adjust the reservation
further.
Since checking for corruption makes the memory unavailable anyway and
since it is now established the memory is too unreliable to use, I am
suggesting removing the check code completely.
The other alternative is to have it optionally scan from the reserved
threshold to some higher point, and only kick in if that gap is nonzero.
That way it doesn't continually run for most users, but it might be
useful to confirm corruption if we explicitly suspect it on some system.
Thoughts?
-hpa
reply other threads:[~2010-08-25 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C75AD28.8060101@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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