On Fri, 2007-07-20 at 08:48 -0700, [EMAIL PROTECTED] wrote: > > Backuping target memory before kexec and restoring it after kexec is > > planed feature for kexec jump. But I will work on image writing/reading > > first. > > if we can get a list of what memory is safe to backup/restore then the > reading/writing of the image should be able to be done in userspace.
The backup/restore here has nothing to do with the read/write of the image. It means instead of preserving memory for a new kernel like that of crash-dump, the memory for a new kernel is backupped before kexec and restored after kexec by the kexec kernel. > > If the "scatter copy" is replaced by "scatter swap", we need not the > > inverse list, and the state of kexeced kernel can be backuped too. There > > are "scatter copy" support in normal kexec implementation in > > "relocate_kernel". > > what do you mean by "scatter swap" copy: dest=src swap: tmp=dest; dest=src; src=tmp If memory is swapped, no information is lost, both that of kexec kernel and kexeced kernel. Best Regards, Huang, Ying - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
