On Tue, 4 Jun 2024 at 17:44, Borislav Petkov <b...@alien8.de> wrote: > > On Tue, Jun 04, 2024 at 09:23:58AM +0800, Dave Young wrote: > > kexec_in_progress is only for checking if this is in a reboot (kexec) code > > path. > > But eif_mem_reserve is only called during the boot time so checking > > kexec_in_progress is meaningless here. > > current_kernel_is_booted_via_kexec != is_rebooting_with_kexec > > That's exactly what I wanna check: whether this is a kexec-ed kernel. Or > is there a better helper for that?
No general way to check if it is a kexec-ed kernel or not, for x86 one can check the efi_setup as Ashish's original patch did, as the kexec booted kernel (efi boot) will have efi setup_data passed in. Otherwise there is a type_of_loader field for x86 boot protocol, kexec-tools is 0x0D, the kexec_file_load also uses this. But adding the type_of_loader was only added in kexec-tools code when Yinghai worked on the kexec-tools bzImage64 load, so older kexec-tools will not set this field. Anyway the in-kernel kexec_file_load code for x86 added 0x0D as loader type from the beginning. Anyway there is not such a helper for all cases. > > -- > Regards/Gruss, > Boris. > > https://people.kernel.org/tglx/notes-about-netiquette > _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
