[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALu+AoStijsAxNvX0h2w7jBt-4sHr0O9AEtyyoxNbLBtgmZB7g@mail.gmail.com>
Date: Fri, 13 Sep 2024 20:52:48 +0800
From: Dave Young <dyoung@...hat.com>
To: Usama Arif <usamaarif642@...il.com>
Cc: Ard Biesheuvel <ardb@...nel.org>, Breno Leitao <leitao@...ian.org>, linux-efi@...r.kernel.org,
kexec@...ts.infradead.org, ebiederm@...ssion.com, bhe@...hat.com,
vgoyal@...hat.com, tglx@...utronix.de, dave.hansen@...ux.intel.com,
x86@...nel.org, linux-kernel@...r.kernel.org, rmikey@...a.com,
gourry@...rry.net
Subject: Re: [RFC] efi/tpm: add efi.tpm_log as a reserved region in 820_table_firmware
Hi Usama,
> > Anyway I was not aware very much about the firmware e820 tables and
> > kexec tables when they were created. I suspect that a cleanup and
> > revisit is needed. I will have a look at that.
>
> Yes, I feel like there is one too many tables! From reading the code
> I understand that /sys/firmware/memmap should contain the untouched map
> at time of boot, i.e. e820_table_firmware. But I would be in favour of
> getting rid of e820_table_firmware, and just having e820_table_kexec.
> And /sys/firmware/memmap gets data from e820_table_kexec.
Agreed, I have the same feelings.
Thanks
Dave
Powered by blists - more mailing lists