From: Avi Kivity <avi@redhat.com>
To: Eric B Munson <emunson@mgebm.net>
Cc: mingo@redhat.com, hpa@zytor.com, arnd@arndb.de,
ryanh@linux.vnet.ibm.com, aliguori@us.ibm.com,
mtosatti@redhat.com, jeremy.fitzhardinge@citrix.com,
kvm@vger.kernel.org, linux-arch@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4 V7] Add ioctl for KVMCLOCK_GUEST_STOPPED
Date: Thu, 22 Dec 2011 12:06:46 +0200 [thread overview]
Message-ID: <4EF30136.2060100@redhat.com> (raw)
In-Reply-To: <1323978126-13222-4-git-send-email-emunson@mgebm.net>
On 12/15/2011 09:42 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.
>
> +4.64 KVMCLOCK_GUEST_PAUSED
> +
> +Capability: basic
> +Architechtures: 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 can be called during unpause, yes? The documentation should reflect
that. I'm thinking of the SIGCONT handler here.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-22 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 19:42 [PATCH 0/4 V7] Avoid soft lockup message when KVM is stopped by host Eric B Munson
2011-12-15 19:42 ` [PATCH 1/4 V7] Add flag to indicate that a vm was stopped by the host Eric B Munson
2011-12-15 19:42 ` [PATCH 2/4 V7] Add functions to check if the host has stopped the vm Eric B Munson
2011-12-15 19:42 ` [PATCH 3/4 V7] Add ioctl for KVMCLOCK_GUEST_STOPPED Eric B Munson
2011-12-22 10:06 ` Avi Kivity [this message]
2011-12-22 10:08 ` Avi Kivity
2011-12-22 10:11 ` Avi Kivity
2011-12-15 19:42 ` [PATCH 4/4 V7] Add check for suspended vm in softlockup detector Eric B Munson
2011-12-16 16:08 ` [PATCH 0/4 V7] Avoid soft lockup message when KVM is stopped by host Arnd Bergmann
2011-12-21 16:27 ` Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF30136.2060100@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=arnd@arndb.de \
--cc=emunson@mgebm.net \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=ryanh@linux.vnet.ibm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.