From: Andy Lutomirski <luto@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>, x86@kernel.org
Cc: Mario Limonciello <mario_limonciello@dell.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 2/2] x86/boot: Simplify EBDA-vs-BIOS reservation logic
Date: Thu, 21 Jul 2016 14:16:52 -0700 [thread overview]
Message-ID: <ef89c0c761be20ead8bd9a3275743e6259b6092a.1469135598.git.luto@kernel.org> (raw)
In-Reply-To: <cover.1469135598.git.luto@kernel.org>
In-Reply-To: <cover.1469135598.git.luto@kernel.org>
Both the intent and the effect of reserve_bios_regions() is simple:
reserve the range from the apparent BIOS start (suitably filtered)
through 1MB and, if the EBDA start address is sensible, extend that
reservation downward to cover the EBDA as well.
The code is overcomplicated, though, and contains head-scratchers
like:
if (ebda_start < BIOS_START_MIN)
ebda_start = BIOS_START_MAX;
That snipped is trying to say "if ebda_start < BIOS_START_MIN,
ignore it".
Simplify it: reorder the code so that it makes sense. This should
have no functional effect under any circumstances.
Signed-off-by: Andy Lutomirski <luto@kernel.org>
---
arch/x86/kernel/ebda.c | 34 +++++++++++-----------------------
1 file changed, 11 insertions(+), 23 deletions(-)
diff --git a/arch/x86/kernel/ebda.c b/arch/x86/kernel/ebda.c
index 6219eef20e2e..4312f8ae71b7 100644
--- a/arch/x86/kernel/ebda.c
+++ b/arch/x86/kernel/ebda.c
@@ -65,22 +65,6 @@ void __init reserve_bios_regions(void)
if (!x86_platform.legacy.reserve_bios_regions)
return;
- /* Get the start address of the EBDA page: */
- ebda_start = get_bios_ebda();
-
- /*
- * Quirk: some old Dells seem to have a 4k EBDA without
- * reporting so in their BIOS RAM size value, so just
- * consider the memory above 640K to be off limits
- * (bugzilla 2990).
- *
- * We detect this case by filtering for nonsensical EBDA
- * addresses below 128K, where we can assume that they
- * are bogus and bump it up to a fixed 640K value:
- */
- if (ebda_start < BIOS_START_MIN)
- ebda_start = BIOS_START_MAX;
-
/*
* BIOS RAM size is encoded in kilobytes, convert it
* to bytes to get a first guess at where the BIOS
@@ -91,18 +75,22 @@ void __init reserve_bios_regions(void)
/*
* If bios_start is less than 128K, assume it is bogus
- * and bump it up to 640K:
+ * and bump it up to 640K. Similarly, if bios_start is above 640K,
+ * don't trust it.
*/
- if (bios_start < BIOS_START_MIN)
+ if (bios_start < BIOS_START_MIN || bios_start > BIOS_START_MAX)
bios_start = BIOS_START_MAX;
+ /* Get the start address of the EBDA page: */
+ ebda_start = get_bios_ebda();
+
/*
- * Use the lower of the bios_start and ebda_start
- * as the starting point, but don't allow it to
- * go beyond 640K:
+ * If the EBDA start address is sane and is below the BIOS region,
+ * then also reserve everything from the EBDA start address up to
+ * the BIOS region.
*/
- bios_start = min(bios_start, ebda_start);
- bios_start = min(bios_start, BIOS_START_MAX);
+ if (ebda_start >= BIOS_START_MIN && ebda_start < bios_start)
+ bios_start = ebda_start;
/* Reserve all memory between bios_start and the 1MB mark: */
memblock_reserve(bios_start, 0x100000 - bios_start);
--
2.7.4
next prev parent reply other threads:[~2016-07-21 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 21:16 [PATCH 0/2] x86/boot: Further reserve_boot_regions() cleanups Andy Lutomirski
2016-07-21 21:16 ` [PATCH 1/2] x86/boot: Clarify what x86_legacy_features.reserve_bios_regions does Andy Lutomirski
2016-07-22 10:25 ` [tip:x86/boot] " tip-bot for Andy Lutomirski
2016-07-21 21:16 ` Andy Lutomirski [this message]
2016-07-22 10:26 ` [tip:x86/boot] x86/boot: Simplify EBDA-vs-BIOS reservation logic tip-bot for Andy Lutomirski
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=ef89c0c761be20ead8bd9a3275743e6259b6092a.1469135598.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mjg59@srcf.ucam.org \
--cc=x86@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
all inboxes | Powered by JetHome®