From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Mike Rapoport <rppt@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Rapoport <rppt@linux.ibm.com>,
untaintableangel@hotmail.co.uk, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/Kconfig: decrease maximum of X86_RESERVE_LOW to 512K
Date: Fri, 28 May 2021 13:20:08 -0700 [thread overview]
Message-ID: <5AFA0407-7F2F-403A-B5BA-7D535993C776@zytor.com> (raw)
In-Reply-To: <YLEBeJwHgnLxRtYW@zn.tnic>
Please just do it. It is insane to spend more effort on reclaiming at the very most a few hundred kilobytes in this day and age.
On May 28, 2021 7:43:04 AM PDT, Borislav Petkov <bp@alien8.de> wrote:
>On Thu, May 27, 2021 at 07:12:51PM -0700, H. Peter Anvin wrote:
>> BIOSes have been known to clobber more than 64K. They aren't supposed
>to
>> clobber any.
>
>Yah, the BIOSes and what they're not supposed to do. Like they even
>care.
>
>> 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."
>
>Right.
>
>So thoughts on:
>
>https://lkml.kernel.org/r/YK%2Bgv0vDfLVD7Sqp@kernel.org
>
>?
>
>Time to do what windoze 7 does?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2021-05-28 20:20 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 [this message]
2021-05-31 9:32 ` David Laight
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=5AFA0407-7F2F-403A-B5BA-7D535993C776@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--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 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.