From: Dan Williams <dan.j.williams@intel.com>
To: Tony Luck <tony.luck@intel.com>, Dan Williams <dan.j.williams@intel.com>
Cc: Ard Biesheuvel <ardb+git@google.com>, <linux-efi@vger.kernel.org>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<dyoung@redhat.com>, "Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [RFC PATCH] x86/efi: Drop support for fake EFI memory maps
Date: Mon, 1 Jul 2024 13:54:24 -0700 [thread overview]
Message-ID: <6683178094c32_5639294c7@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <ZoMUnSaqORagM_Y2@agluck-desk3.sc.intel.com>
Tony Luck wrote:
> On Mon, Jul 01, 2024 at 01:17:01PM -0700, Dan Williams wrote:
> > [ add Tony who may care about the more-reliable removal ]
>
> I don't think I care about removal the fake options. I have had
> systems that support real "more-reliable" memory for many years.
Ok, lets remove it and see what happens. I recall now that the major
policy knob that users may care about is efi=nosoftreserve, and the
ability to specify efi_fake_mem for testing purposes can move to memmap=
on the assumption that kernel-devs are much less likely to specify
broken settings, or at least can pick up the pieces.
Ard, you can add:
Acked-by: Dan Williams <dan.j.williams@intel.com>
next prev parent reply other threads:[~2024-07-01 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 7:32 [RFC PATCH] x86/efi: Drop support for fake EFI memory maps Ard Biesheuvel
2024-07-01 12:47 ` Borislav Petkov
2024-07-01 13:27 ` Ard Biesheuvel
2024-07-01 20:17 ` Dan Williams
2024-07-01 20:42 ` Tony Luck
2024-07-01 20:54 ` Dan Williams [this message]
2024-07-01 22:25 ` Ard Biesheuvel
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=6683178094c32_5639294c7@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=dyoung@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.