Hi! > This patch implement the functionality of jumping from kexeced kernel > to original kernel. > > A new reboot command named LINUX_REBOOT_CMD_KJUMP is defined to > trigger the jumping to (executing) the new kernel or jumping back to > the original kernel. Could we get two reboot commands? Exec loaded kernel seems to be quite different operation than "jump back". How do I test these patches? kexec -p <bzImage>, then kexec -j? > +static unsigned long kexec_backup_addr = ~0UL; > + > +/* kexec_backup= specifies the location of backuped 0~640k memory of > + * crashed kernel. > + */ > +static int __init parse_kexec_backup(char *arg) > +{ > + if (!arg) > + return -EINVAL; > + > + kexec_backup_addr = memparse(arg, &arg); > + return 0; > +} > +early_param("kexec_backup", parse_kexec_backup); New kernel parameters should be documented. (Plus I do not know how to use this one, please help :-). > +int kexec_flags; > + > +static unsigned long kexec_jump_buf_pfn; > + > +static int __init parse_kexec_jump_buf_pfn(char *arg) > +{ > + if (!arg) > + return -EINVAL; > + > + kexec_jump_buf_pfn = memparse(arg, &arg); > + kexec_flags |= KEXEC_FLAGS_IS_KEXECED_KERNEL; > + return 0; > +} > +early_param("kexec_jump_buf_pfn", parse_kexec_jump_buf_pfn); This one should be documented, too, I'd guess. (Is that internal, kernel-to-kernel communication?) Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm