[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc655618-9e30-9377-4fcf-c967707b4b0b@intel.com>
Date: Thu, 1 Jul 2021 10:15:29 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Mike Rapoport <rppt@...nel.org>, x86@...nel.org
Cc: "H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...capital.net>,
Andy Shevchenko <andy@...radead.org>,
Ard Biesheuvel <ardb@...nel.org>, Baoquan He <bhe@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Darren Hart <dvhart@...radead.org>,
Dave Young <dyoung@...hat.com>,
Hugh Dickins <hughd@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Jonathan Corbet <corbet@....net>,
Lianbo Jiang <lijiang@...hat.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Randy Dunlap <rdunlap@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-doc@...r.kernel.org, linux-efi@...r.kernel.org,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH 1/3] x86/setup: always reserve the first 1M of RAM
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.
Powered by blists - more mailing lists