"Huang, Ying" <ying.huang at intel.com> writes: > The disadvantage of this solution is that kernel B must know it is > original kernel (A) or kexeced kernel (B). Different code should be used > by kernel A and kernel B. And after jump from A to B, jump from B to A, > when jump from A to B again, kernel A must use different code from the > first time. I don't know what the case is for keeping two kernels in memory and switching between them. I suspect a small piece of trampoline code between the two kernels could handle the case. (i.e. purgatory pays attention). That is a fundamental aspect of the design. A general purpose infrastructure with trampoline code to adapt it to whatever situation comes up. Eric
