KVM: x86: Add ioctl for KVM_KVMCLOCK_CTRL
Now that we have a flag that will tell the guest it was suspended, create an interface for that communication using a KVM ioctl. Signed-off-by: Eric B Munson <emunson@mgebm.net> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com>
This commit is contained in:

committed by
Avi Kivity

parent
3b5d56b931
commit
1c0b28c2a4
@@ -1669,6 +1669,26 @@ at the memory location pointed to by "addr".
|
||||
The list of registers accessible using this interface is identical to the
|
||||
list in 4.64.
|
||||
|
||||
4.70 KVM_KVMCLOCK_CTRL
|
||||
|
||||
Capability: KVM_CAP_KVMCLOCK_CTRL
|
||||
Architectures: Any that implement pvclocks (currently x86 only)
|
||||
Type: vcpu ioctl
|
||||
Parameters: None
|
||||
Returns: 0 on success, -1 on error
|
||||
|
||||
This signals to the host kernel that the specified guest is being paused by
|
||||
userspace. The host will set a flag in the pvclock structure that is checked
|
||||
from the soft lockup watchdog. The flag is part of the pvclock structure that
|
||||
is shared between guest and host, specifically the second bit of the flags
|
||||
field of the pvclock_vcpu_time_info structure. It will be set exclusively by
|
||||
the host and read/cleared exclusively by the guest. The guest operation of
|
||||
checking and clearing the flag must an atomic operation so
|
||||
load-link/store-conditional, or equivalent must be used. There are two cases
|
||||
where the guest will clear the flag: when the soft lockup watchdog timer resets
|
||||
itself or when a soft lockup is detected. This ioctl can be called any time
|
||||
after pausing the vcpu, but before it is resumed.
|
||||
|
||||
5. The kvm_run structure
|
||||
|
||||
Application code obtains a pointer to the kvm_run structure by
|
||||
|
Reference in New Issue
Block a user