cpu/kvm/base.hh

69  * state synchronization between gem5 and KVM.
121     /** Dump the internal state to the terminal. */
133      * A cached copy of a thread's state in the form of a SimpleThread
136      * Normally the actual thread state is stored in the KVM vCPU. If KVM has
138      * some events within gem5 that required state to be updated this could be
142      * KVM state is dirty (i.e., the vCPU has been run since the last
148      * objects to modify this thread's state.
183          * The CPU generally enters this state when the guest execute
186          * scheduled in this state.
193          * This is the normal run state of the CPU. KVM will be
200          * will call handleKvmExit() on the next cycle. The next state
216          *  will transition to the RunningServiceCompletion state.
222          * entered once in order to get to a consistent state. This
225          * the Running or RunningService state.
230     /** CPU run state */
268      * make sure that the KVM state is synchronized and that the TC is
271      * @note This method does not normally cause any state
273      * the thread, which leads to a transition to the Idle state. In
340      * Get/Set the register state of the guest vCPU
342      * KVM has two different interfaces for accessing the state of the
356      * Get/Set the guest FPU/vector state
358     void getFPUState(struct kvm_fpu &state) const;
359     void setFPUState(const struct kvm_fpu &state);
396      * Update the KVM state from the current thread context
400      * CPU implementation is expected to update all guest state
401      * (registers, special registers, and FPU state).
406      * Update the current thread context with the KVM state
408      * The base CPU after the guest updates any of the KVM state. In
410      * dependent code is expected to read the state of the guest CPU
411      * and update gem5's thread state.
416      * Update a thread context if the KVM state is dirty with respect
508      * Is the architecture specific code in a state that prevents
512      * in the guest vCPU that won't be carried over to the gem5 state
593         /** Returns next valid state after one or more IO accesses */
626      * the KVM vCPU state upon the next call to kvmRun().
631      * Is the KVM state dirty? Set to true to force an update of
632      * the KVM vCPU state upon the next call to kvmRun().