From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Olof Johansson <olof@lixom.net>, "H. Peter Anvin" <hpa@linux.intel.com>
Subject: [RFC PATCH 0/3] x86, boot: Low memory reservation fixes
Date: Mon, 11 Nov 2013 16:16:44 -0800 [thread overview]
Message-ID: <1384215407-22288-1-git-send-email-hpa@linux.intel.com> (raw)
From: "H. Peter Anvin" <hpa@linux.intel.com>
On all but the tiniest of modern systems, losing half a megabyte of
RAM is a small price to pay for system stability. Thus, switch the
default for low memory reservation to 640K. This has been possible,
but has not been the default, since v3.9, specifically checkin:
95c9608478d6 x86, mm: Move reserving low memory later in initialization
The above checkin exposes a problem with our reservation ordering;
specifically setup_bios_corruption_check() is called too early, so fix
that. This caused the BIOS corruption check to run on memory that
would have been reserved anyway.
Finally, change the low memory check scanner to scan 640K rather than
64K by default. The low memory check scanner will be a noop in the
common case, as it now will only grab memory that is not otherwise
reserved; this makes it purely a diagnostic tool.
H. Peter Anvin (3):
x86, boot: Move setup_bios_corruption_check() later
x86, boot: Change the default for X86_RESERVE_LOW to 640K, make EXPERT
x86, boot: Change the BIOS corruption checker to scan 640K
next reply other threads:[~2013-11-12 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 0:16 H. Peter Anvin [this message]
2013-11-12 0:16 ` [RFC PATCH 1/3] x86, boot: Move setup_bios_corruption_check() later H. Peter Anvin
2013-11-12 0:16 ` [RFC PATCH 2/3] x86, boot: Change the default for X86_RESERVE_LOW to 640K, make EXPERT H. Peter Anvin
2013-11-12 0:16 ` [RFC PATCH 3/3] x86, boot: Change the BIOS corruption checker to scan 640K H. Peter Anvin
2013-11-12 4:07 ` Ingo Molnar
2013-11-12 7:19 ` H. Peter Anvin
2013-11-12 9:42 ` Ingo Molnar
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=1384215407-22288-1-git-send-email-hpa@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=olof@lixom.net \
--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 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.