Joerg Roedel wrote: > On Mon, Apr 14, 2008 at 01:29:50PM +0300, Avi Kivity wrote: > >> Joerg Roedel wrote: >> >>> Only the state saved in the VMCB is undefined after an intercepted >>> shutdown event. >>> >> The vmcb stores two types of states, guest state and control >> information. Are both undefined? >> > > Only the guest state is undefined. > >
Okay, so we don't need to init_vmcb() there. We can just reset the processor (actually, we should rely on userspace to reset the processor; IIRC shutdown does not reset the processor directly; instead the system board detects the shutdown and converts it to a reset, and we may want to emulate other types of system boards). >>> I am not sure if I understand your second question, what >>> do you mean with "core melting down" vs. guest initiated shutdown? >>> >>> >> IIRC shutdown can occur not only as a result of triple faults, due to >> other internal errors or inconsistent state. Not sure about that >> though. >> > > No, there is no way to to differentiate between a shutdown caused by a > triple fault and other shutdown situations. If the shutdown event is > caused by a too hot processor it is not intercepted. This situation is > handled like a normal cpu shutdown. > Well, that gives you some differentiation (enough for our needs). -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
