From: Eric B Munson <emunson@mgebm.net>
To: avi@redhat.com
Cc: mingo@redhat.com, hpa@zytor.com, ryanh@linux.vnet.ibm.com,
aliguori@us.ibm.com, mtosatti@redhat.com, kvm@vger.kernel.org,
linux-arch@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4 V13] Add ioctl for KVM_KVMCLOCK_CTRL
Date: Thu, 16 Feb 2012 15:22:15 -0500 [thread overview]
Message-ID: <20120216202215.GA8090@mgebm.net> (raw)
In-Reply-To: <1329423541-11677-4-git-send-email-emunson@mgebm.net>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
On Thu, 16 Feb 2012, 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.
>
> Signed-off-by: Eric B Munson <emunson@mgebm.net>
Sorry, this is actually V14.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-16 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 20:18 [PATCH 0/4 V14] Avoid soft lockup message when KVM is stopped by host Eric B Munson
2012-02-16 20:18 ` [PATCH 1/4 V14] Add flag to indicate that a vm was stopped by the host Eric B Munson
2012-02-16 20:18 ` [PATCH 2/4 V14] Add functions to check if the host has stopped the vm Eric B Munson
2012-02-16 20:19 ` [PATCH 3/4 V13] Add ioctl for KVM_KVMCLOCK_CTRL Eric B Munson
2012-02-16 20:22 ` Eric B Munson [this message]
2012-02-18 10:30 ` Avi Kivity
2012-02-16 20:19 ` [PATCH 4/4 V14] Add check for suspended vm in softlockup detector Eric B Munson
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 15:07 [PATCH 0/4 V13] Avoid soft lockup message when KVM is stopped by host Eric B Munson
2012-02-08 15:07 ` [PATCH 3/4 V13] Add ioctl for KVM_KVMCLOCK_CTRL Eric B Munson
2012-02-16 14:11 ` Avi Kivity
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=20120216202215.GA8090@mgebm.net \
--to=emunson@mgebm.net \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=hpa@zytor.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.