Re: [PATCH 4/5] kexec: fallback to KEXEC_LOAD when KEXEC_FILE_LOAD is not supported.

On Fri, 2 Mar 2018 17:17:06 +0800 Dave Young wrote: > On 02/26/18 at 01:00pm, Michal Suchanek wrote: > > Not all architectures implement KEXEC_FILE_LOAD. However, on some > > archiectures KEXEC_FILE_LOAD is required when secure boot is > > enabled in locked-down mode.

[PATCH v2 2/3] arm64: Add support to read symbols like _stext from '/proc/kallsyms'

On ARM64 platforms the VA_BITS supported by a linux kernel being run can be selected by setting 'ARM64_VA_BITS_*' (see 'arch/arm64/Kconfig' for details). Now, to determine the 'info->page_offset' in arm64 makedumpfile context ('arch/arm64.c') we need to determine the VA_BITS which was selected by

[PATCH v2 3/3] Documentation: Update documentation regarding --mem-usage' option

Earlier patch in this patchset, enables the '--mem-usage' makedumpfile option on arm64 platforms. In addition, I have validated the '--mem-usage' makedumpfile option on several ppc64/ppc64le and s390x machines, so update the 'makedumpfile.8' documentation to indicate that '--mem-usage' option is

[PATCH] kexec: add option to fall back to KEXEC_LOAD when KEXEC_FILE_LOAD is not supported.

Not all architectures implement KEXEC_FILE_LOAD. However, on some archiectures KEXEC_FILE_LOAD is required when secure boot is enabled in locked-down mode. Previously users had to select the KEXEC_FILE_LOAD syscall with undocumented -s option. However, if they did pass the option kexec would fail

RE: [PATCH makedumpfile] handle mem_section as either a pointer or an array

Hi Thadeu, Sorry for the late reply. "handle mem_section as either a pointer or an array" patch and "Always use bigger SECTION_MAP_MASK" patch modify the same line. I would like to reply about both patches by the end of the next week. Thanks Tachibana > -Original Message- > From: