From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, dionnaglaze@google.com
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Ard Biesheuvel <ardb@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
x86@kernel.org, jiewen.yao@intel.com,
"Min M. Xu" <min.m.xu@intel.org>,
James Bottomley <jejb@linux.ibm.com>,
Tom Lendacky <Thomas.Lendacky@amd.com>,
Erdem Aktas <erdemaktas@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [edk2-devel] [PATCH v2] x86/efi: Safely enable unaccepted memory in UEFI
Date: Wed, 18 Jan 2023 08:51:40 +0100 [thread overview]
Message-ID: <20230118075140.6pyszln4ovi2htxk@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAAH4kHbhSfeDeBCLCO4Bc2MK8Ds-kjXxCnrkMEP1j_GO5sh18w@mail.gmail.com>
Hi,
> To Gerd's point, removing "first in edk2, later in linux too" I think
> is backwards. We need all users of the protocol to agree that SEV-SNP
> and TDX strictly imply unaccepted memory support. Only then can we
> remove the protocol from EDK2.
Its not backwards.
edk2 dropping support first would result in break kernels without
support for unaccepted memory. Which is why we wait until such
kernels are EOL.
Linux dropping support first would result in firmware accepting all
memory again. So that isn't a good plan. Thats why linux should
support the protocol a bit longer, while firmware versions which
expect negotiation happening are still in use.
take care,
Gerd
next prev parent reply other threads:[~2023-01-18 7:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 21:29 [PATCH v2] x86/efi: Safely enable unaccepted memory in UEFI Dionna Glaze
2023-01-13 22:20 ` Kirill A. Shutemov
2023-01-16 10:56 ` Gerd Hoffmann
2023-01-16 12:30 ` Kirill A. Shutemov
2023-01-16 13:11 ` Ard Biesheuvel
2023-01-16 13:42 ` Kirill A. Shutemov
2023-01-16 19:43 ` Dionna Glaze
2023-01-16 23:17 ` Kirill A. Shutemov
2023-01-17 10:24 ` Gerd Hoffmann
2023-01-17 16:45 ` Dionna Glaze
2023-01-18 7:51 ` Gerd Hoffmann [this message]
2023-01-16 21:22 ` Dave Hansen
2023-01-16 22:46 ` Lendacky, Thomas
2023-01-18 15:09 ` Ard Biesheuvel
2023-01-18 15:40 ` Dave Hansen
2023-01-18 15:46 ` Ard Biesheuvel
2023-01-17 10:34 ` Gerd Hoffmann
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-list 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=20230118075140.6pyszln4ovi2htxk@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/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