public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: "'H. Peter Anvin'" <hpa@zytor.com>,
	Borislav Petkov <bp@alien8.de>, "Mike Rapoport" <rppt@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Mike Rapoport <rppt@linux.ibm.com>,
	"untaintableangel@hotmail.co.uk" <untaintableangel@hotmail.co.uk>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] x86/Kconfig: decrease maximum of X86_RESERVE_LOW to 512K
Date: Mon, 31 May 2021 09:32:22 +0000	[thread overview]
Message-ID: <8f74d4bd0d97445c8a976eab44fc9372@AcuMS.aculab.com> (raw)
In-Reply-To: <f7525409-3987-f79d-9f52-71f6c0231491@zytor.com>

From: H. Peter Anvin
> Sent: 28 May 2021 03:13
....
> BIOSes have been known to clobber more than 64K. They aren't supposed to
> clobber any.

They probably shouldn't need anything above the base of the DOS
transient program area preserved.
Can't remember where that is though :-(

It is hard enough finding a safe memory area for the MBR
code to relocate itself to before loading the PBR.
Both the MBR and PBR load at the same address - 0xc00.

> 640K is the limit because that is the address of the EGA/VGA frame
> buffer. In the words of Bill Gates "640K ought to be enough for anyone."

I thought the original memory map allocated 512K for memory
and 512k for memory mapped I/O.
No one could afford more then 512K DRAM :-)

The 640K limit appears because nothing was actually mapped
as the bottom of the 'I/O area' so memory could expand up
that far.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  parent reply	other threads:[~2021-05-31  9:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  8:11 [PATCH] x86/Kconfig: decrease maximum of X86_RESERVE_LOW to 512K Mike Rapoport
2021-05-26  8:47 ` Borislav Petkov
2021-05-26 16:30   ` Mike Rapoport
2021-05-26 18:14     ` Borislav Petkov
2021-05-27 13:38       ` Mike Rapoport
2021-05-28 14:41         ` Borislav Petkov
2021-05-28  2:12       ` H. Peter Anvin
2021-05-28 14:43         ` Borislav Petkov
2021-05-28 20:20           ` H. Peter Anvin
2021-05-31  9:32         ` David Laight [this message]
2021-05-31 12:59           ` H. Peter Anvin

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=8f74d4bd0d97445c8a976eab44fc9372@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rppt@kernel.org \
    --cc=rppt@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=untaintableangel@hotmail.co.uk \
    --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