[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALu+AoTgjdq+kUbv-5CGQr=UTLd2+zDLbHt=kXaoMYYptBYnAA@mail.gmail.com>
Date: Fri, 10 Jan 2025 10:50:30 +0800
From: Dave Young <dyoung@...hat.com>
To: Usama Arif <usamaarif642@...il.com>
Cc: linux-efi@...r.kernel.org, devel@...2.groups.io, kexec@...ts.infradead.org,
ardb@...nel.org, hannes@...xchg.org, x86@...nel.org,
linux-kernel@...r.kernel.org, leitao@...ian.org, gourry@...rry.net,
kernel-team@...a.com
Subject: Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved
region in 820_table_firmware
Hi Usama,
On Thu, 9 Jan 2025 at 06:00, Usama Arif <usamaarif642@...il.com> wrote:
>
> When this area is not reserved, it comes up as usable in
> /sys/firmware/memmap. This means that kexec, which uses that memmap
> to find usable memory regions, can select the region where
> efi_mem_attr_table is and overwrite it and relocate_kernel.
Is the attr table BOOT SERVICE DATA? If so, does efi_mem_reserve()
work for you?
Just refer to esrt.c.
Thanks
Dave
Powered by blists - more mailing lists