Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM

[PATCH 0/3] x86/setup: always resrve the first 1M of RAM · Mike Rapoport <rppt@kernel.org> · 2021-06-01
[PATCH 1/3] x86/setup: always reserve the first 1M of RAM · Mike Rapoport <rppt@kernel.org> · 2021-06-01
Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM · Baoquan He <hidden> · 2021-06-01
Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM · Mike Rapoport <rppt@kernel.org> · 2021-06-01
Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM · Borislav Petkov <bp@alien8.de> · 2021-06-03
Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM · Dave Hansen <hidden> · 2021-07-01
Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM · Mike Rapoport <rppt@kernel.org> · 2021-07-01
[PATCH 2/3] x86/setup: remove CONFIG_X86_RESERVE_LOW and reservelow options · Mike Rapoport <rppt@kernel.org> · 2021-06-01
[PATCH 3/3] x86/crash: remove crash_reserve_low_1M() · Mike Rapoport <rppt@kernel.org> · 2021-06-01
Re: [PATCH 0/3] x86/setup: always resrve the first 1M of RAM · Hugh Dickins <hughd@google.com> · 2021-06-01

From: Dave Hansen <hidden>
Date: 2021-07-01 17:15:41
Also in: linux-efi, lkml, platform-driver-x86

On 6/1/21 12:53 AM, Mike Rapoport wrote:

There are BIOSes that are known to corrupt the memory under 1M, or more
precisely under 640K because the memory above 640K is anyway reserved for
the EGA/VGA frame buffer and BIOS.

Should there have been a Cc: stable@ on this?

Seems like the kind of thing we'd want backported.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help