On Wed, Mar 12, 2008 at 09:45:26AM +0800, Huang, Ying wrote: [..] > > I have thought through it again and try to put together some of the > > new kexec options we can introduce to make the whole thing work. I am > > considering a simple case where a user boots the kernel A and then > > launches kernel B using "kexec --load-preseve-context". Now a user > > might save the hibernated image or might want to come back to A. > > > > - kexec -l <kernel-image> > > Normal kexec functionality. Boot a new kernel, without preserving > > existing kernel's context. > > > > - kexec --load-preserve-context <kernel-image> > > Boot a new kernel while preserving existing kernel's context. > > > > Will be used for booting kernel B for the first time. > > > > - kexec --load-resume-image <resumable-core> > > In original kexec-tools, this can be done through: > kexec -l --args-none <resumable-core> > > Do you need to define an alias for it? Ok, we can get rid of --load-resume-image and go by the Eric's idea of detecting image type and taking action accordingly. Thanks Vivek _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
