On 02/08/2012 05:07 PM, Eric B Munson wrote: > Now that we have a flag that will tell the guest it was suspended, create an > interface for that communication using a KVM ioctl. > > + > +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. This needs to be expanded. There is a protocol between the host and guest that needs to be documented, including the requirement to use a single instruction (or ll/sc) to clear the flag. See Documentation/virtual/kvm/msr.txt > This ioctl can be called during pause or > +unpause. > + After pausing the vcpu, but before resuming it. -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
