Jan Kiszka wrote:
Jan Kiszka wrote: ..Index: b/arch/x86/kvm/vmx.c =================================================================== --- a/arch/x86/kvm/vmx.c +++ b/arch/x86/kvm/vmx.c @@ -90,6 +90,11 @@ struct vcpu_vmx { } rmode; int vpid; bool emulation_required; + + /* Support for vnmi-less CPUs */ + int soft_vnmi_blocked; + ktime_t entry_time; + s64 vnmi_blocked_time;I meanwhile realized that these states (except entry_time) and probably also arch.nmi_pending/injected are things that should be considered when the vcpu state is saved and restored, right? What is the right interface for this? An extension of kvm_sregs?
kvm_sregs can't be extended because that would break the ABI, so we have to add a new ioctl.
I have some patches that allow ioctls to be extended, so if that's accepted, we can avoid the new ioctl.
BTW, via which channel is GUEST_INTERRUPTIBILITY_INFO from the vmcs saved/restored? I'm currently not seeing any related, CPU-specific code.
Looks like it's missing. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
