On Fri, 2 Mar 2018 13:44:58 +0100 Simon Horman <ho...@verge.net.au> wrote:
> On Mon, Feb 26, 2018 at 01:00:37PM +0100, 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. Previously users had to select the > > KEXEC_FILE_LOAD syscall with undocumented -s option. However, if > > they did pass the option kexec would fail on architectures that do > > not support it. > > > > When no option is passed to select one syscall or the other try > > KEXEC_FILE_LOAD and fall back to KEXEC_LOAD when not suported. > > Has there been a release of kexec-tools with things arranged they > way they currently are? $ git tag --contains 046d1755d2bd723a11a180c265e61a884990712e v2.0.10 v2.0.10-rc1 v2.0.11 v2.0.11-rc1 v2.0.12 v2.0.12-rc1 v2.0.13 v2.0.13-rc1 v2.0.14 v2.0.14-rc1 v2.0.15 v2.0.15-rc1 v2.0.16-rc1 v2.0.8 v2.0.8-rc1 v2.0.9 v2.0.9-rc1 > > Can we document this behaviour and the related undocumented options? It's done in a followup patch. Thanks Michal _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
