On Wed, 17 Mar 09:54, Lin Feng wrote:
After more than one month testing, we find that it is not suitable to process
e820 directly in kexec to place the kernel code. Some regions, like tmplog
and memattr tables, are not marked as reserved in e820.
Take tmplog, for example, the memory of table is
weidong (C)
> ; Wangjing (Hogan, Cloud Infrastructure
> Service Product Dept.) ; Wangxin (Alexander)
> ; Linux Kernel Mailing List
> ; Eric W. Biederman
> Subject: Re: [PATCH] x86/kaslr: try process e820 entries if can not get
> suitable
> regions from efi
>
> On Tu
On Tue, Jan 05, 2021 at 09:54:52AM +0100, Ard Biesheuvel wrote:
> (cc Arvind)
>
> On Tue, 5 Jan 2021 at 09:54, Lin Feng wrote:
> >
> > On efi64 x86_64 system, the EFI_CONVENTIONAL_MEMORY regions will not
> > be mapped when making EFI runtime calls. So kexec-tools can not get
> > these from
(cc Arvind)
On Tue, 5 Jan 2021 at 09:54, Lin Feng wrote:
>
> On efi64 x86_64 system, the EFI_CONVENTIONAL_MEMORY regions will not
> be mapped when making EFI runtime calls. So kexec-tools can not get
> these from /sys/firmware/efi/runtime-map. Then compressed boot os
> can not get suitable
On efi64 x86_64 system, the EFI_CONVENTIONAL_MEMORY regions will not
be mapped when making EFI runtime calls. So kexec-tools can not get
these from /sys/firmware/efi/runtime-map. Then compressed boot os
can not get suitable regions in process_efi_entries and print debug
message as follow:
5 matches
Mail list logo