From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dionna Glaze <dionnaglaze@google.com>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
x86@kernel.org, jiewen.yao@intel.com, devel@edk2.groups.io,
Ard Biescheuvel <ardb@kernel.org>,
"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: [PATCH v2] x86/efi: Safely enable unaccepted memory in UEFI
Date: Tue, 17 Jan 2023 11:34:51 +0100 [thread overview]
Message-ID: <20230117103451.74k6eddipikhml3y@sirius.home.kraxel.org> (raw)
In-Reply-To: <def9b0b5-b880-be99-fa95-b05d76a91824@intel.com>
Hi,
> In any case, the firmware side of things didn't seem like _that_ much
> code. So, I'm not protesting *that* strongly. But, I also don't
> believe for a second that this is going to be removed in 3-5 years.
If things are going roughly as I expect them to go (both tdx support and
unaccepted memory support land upstream this year; distros enable it by
default) we should be able to drop this when the 6.1-lts kernel goes
EOL. First in edk2, later in linux too.
take care,
Gerd
prev parent reply other threads:[~2023-01-17 10:35 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 ` [edk2-devel] " Gerd Hoffmann
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 [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-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=20230117103451.74k6eddipikhml3y@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