From: Nicolas Saenz Julienne <nsaenz@amazon.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Sai Praneeth <sai.praneeth.prakhya@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stanspas@amazon.de>, <nh-open-source@amazon.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] x86/efi: Apply EFI Memory Attributes after kexec
Date: Tue, 12 Nov 2024 09:01:30 +0000 [thread overview]
Message-ID: <D5K2TFWWW4RA.11BRVB9L59S0V@amazon.com> (raw)
In-Reply-To: <CAMj1kXH2FRxwryJ9kz4CThWG_D30nW6g-UJzxW9uRQzBAZEetA@mail.gmail.com>
On Tue Nov 12, 2024 at 7:55 AM UTC, Ard Biesheuvel wrote:
> On Mon, 11 Nov 2024 at 22:45, Nicolas Saenz Julienne <nsaenz@amazon.com> wrote:
>>
>> - Although care is taken to make sure the memory backing the EFI Memory
>> Attributes table is preserved during runtime and reachable after kexec
>> (see efi_memattr_init()). I don't see the same happening for the EFI
>> properties table. Maybe it's just unnecessary as there's an assumption
>> that the table will fall in memory preserved during runtime? Or for
>> another reason? Otherwise, we'd need to make sure it isn't possible to
>> set EFI_NX_PE_DATA on kexec.
>
> Thanks.
>
> I think we should just drop support for the EFI_PROPERTIES_TABLE - it
> was a failed, short-lived experiment that broke the boot on both Linux
> and Windows, and was replaced with the memory attributes table shortly
> after.
Isn't there a tiny posibility some platorm might be using the feature?
Otherwise I'll send a v2 right away.
Nicolas
prev parent reply other threads:[~2024-11-12 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 21:45 [PATCH] x86/efi: Apply EFI Memory Attributes after kexec Nicolas Saenz Julienne
2024-11-12 7:55 ` Ard Biesheuvel
2024-11-12 9:01 ` Nicolas Saenz Julienne [this message]
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=D5K2TFWWW4RA.11BRVB9L59S0V@amazon.com \
--to=nsaenz@amazon.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=nh-open-source@amazon.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=stable@vger.kernel.org \
--cc=stanspas@amazon.de \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox