[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMj1kXGThVygFZNry+tBGdzw0XrFhOiWL_RFYRBy7p1oyT4LOQ@mail.gmail.com>
Date: Wed, 2 Aug 2023 19:06:05 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>
Cc: linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
x86@...nel.org
Subject: Re: [PATCH v2] efi/x86: Ensure that EFI_RUNTIME_MAP is enabled for kexec
On Wed, 2 Aug 2023 at 18:46, Kirill A . Shutemov
<kirill.shutemov@...ux.intel.com> wrote:
>
> On Wed, Aug 02, 2023 at 05:17:04PM +0200, Ard Biesheuvel wrote:
> > CONFIG_EFI_RUNTIME_MAP needs to be enabled in order for kexec to be able
> > to provide the required information about the EFI runtime mappings to
> > the incoming kernel, regardless of whether kexec_load() or
> > kexec_file_load() is being used. Without this information, kexec boot in
> > EFI mode is not possible.
> >
> > The CONFIG_EFI_RUNTIME_MAP option is currently directly configurable if
> > CONFIG_EXPERT is enabled, so that it can be turned on for debugging
> > purposes even if KEXEC is. However, the upshot of this is that it can
>
> s/is/isn't/ ?
>
indeed, will fix.
Powered by blists - more mailing lists