On 08/01/2018 11:35, David Hildenbrand wrote: > Thinking about it, I agree. It might be simpler/cleaner to transfer the > "loaded" VMCS. But I think we should take care of only transferring data > that actually is CPU state and not special to our current > implementation. (e.g. nested_run_pending I would says is special to out > current implementation, but we can discuss) > > So what I would consider VMX state: > - vmxon > - vmxon_ptr > - vmptr > - cached_vmcs12 > - ... ? nested_run_pending is in the same boat as the various KVM_GET_VCPU_EVENTS flags (e.g. nmi.injected vs. nmi.pending). It's not "architectural" state, but it's part of the state machine so it has to be serialized. Thanks, Paolo
