Lines Matching refs:state
369 // Running state, but the architecture specific code might be
376 // The state of the CPU is consistent, so we don't need to do
378 // tick event and enter the Idle state to prevent nasty things
397 // the RunningService state, but the results have still not
399 // update the register state ourselves instead of letting KVM
418 panic("KVM: Unhandled CPU state in drain()\n");
497 // Force an update of the KVM state here instead of flagging the
500 // state to be dumped before and after a takeover.
624 // handleKvmExit() will determine the next state of the CPU
645 // We might need to update the KVM state.
658 // takes care to run until it is in a state where it can
672 // context from KVM if we want to access it. Flag the KVM state as
679 // Enter into the RunningService state unless the
699 panic("BaseKvmCPU entered tick() in an illegal state (%i)\n",
713 // RunningServiceCompletion or RunningMMIOPending state.
779 // state update might affect guest cycle counters.
871 BaseKvmCPU::getFPUState(struct kvm_fpu &state) const
873 if (ioctl(KVM_GET_FPU, &state) == -1)
874 panic("KVM: Failed to get guest FPU state\n");
878 BaseKvmCPU::setFPUState(const struct kvm_fpu &state)
880 if (ioctl(KVM_SET_FPU, (void *)&state) == -1)
881 panic("KVM: Failed to set guest FPU state\n");
996 // Switch into the running state by default. Individual handlers
1330 "tryDrain: CPU transitioned into the Idle state, drain done\n");