[PATCH 0/2 v6] add reserved e820 ranges to the kdump kernel e820 table

At present, when use the kexec_file_load syscall to load the kernel image and initramfs(for example: kexec -s -p xxx), the upstream kernel does not pass the e820 reserved ranges to the second kernel, which might produce two problems: The first one is the MMCONFIG issue, although which does not

[PATCH 2/2 v6] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table

At present, when use the kexec_file_load syscall to load the kernel image and initramfs(for example: kexec -s -p xxx), the upstream kernel does not pass the e820 reserved ranges to the second kernel, which might produce two problems: The first one is the MMCONFIG issue, although which does not

[PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

When load the kernel image and initramfs by kexec_file_load syscall, it can not add exact e820 reserved type to kdump kernel e820 table. Kdump uses walk_iomem_res_desc() to iterate io resources, then adds matched desc to e820 table for kdump kernel. But, when convert the e820 type into the iores

Re: [PATCH v2] lockdown: allow kexec_file of unsigned images when not under lockdown

Hi Thadeu, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.20-rc1 next-20181106] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: