![]() | ||||||||||
Messages in this thread |
--- Werner Almesberger <wa@almesberger.net> wrote: [snip] > An older or newer kernel would have different data structures, and > possibly even data structures which are arranged in a different way > (e.g. a hash becomes some kind of tree, etc.). So you'd need some > translation mechanism that "upgrades" or "downgrades" all kernel > data, including all pointers and offsets that may be sitting > around somewhere. Good luck :-) what if the new kernel asked the old kernel to hand over the data in a form that was understood universally beginning at some kernel version X (earliest supported kernel in other words). the data would not have to remain in the optimized form that it would reside in while under normal operations. it could be serialized as such into a form that simply contains its content and context. im thinking of something along the lines of a data packet (tcp/ip comes to mind) that contains data about its data. a structure similar to that, which conveys information describing the data its contains. any mechanisms the newer kernel may institute would get set to a default state similar to booting just that portion of the kernel. > > Your best bet would be to use a system that already implements some > form of checkpointing or process migration, and use this to > preserve user space state across kexec reboots. openMosix may be [snip] preserving user state would not be so much the problem as would the various internal kernel data structures (vm stuff, dcache, etc.) the issue here is to freeze the system state, sys calls, irqs, and all, and restart the same state where it left off after the switch. the kernel would not need to boot, as an initial boot has already been done by the previous kernel. yes, it would be extremely difficult. but, as with all fields of endevour, a holy grail is only such because it is. the question remains, is this do-able? perhaps not now, or in two years, but what about five? say, kernel 3.x.x or even 4.x.x? ===== Main Entry: anom | |||||||||
| Last update: 2005-03-22 11:31 [W:2.066 / U:0.180 seconds] ©2003-2008 Jasper Spaans | ||||||||||