[lkml]   [2012]   [Feb]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 3/4 V13] Add ioctl for KVM_KVMCLOCK_CTRL
    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

    > 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

     \ /
      Last update: 2012-02-16 15:15    [W:0.019 / U:7.080 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site