All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Eric B Munson <emunson@mgebm.net>
Cc: avi@redhat.com, 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/5 V4] Add ioctl for KVM_GUEST_STOPPED
Date: Sat, 03 Dec 2011 11:16:14 +0200	[thread overview]
Message-ID: <1322903774.3782.1.camel@lappy> (raw)
In-Reply-To: <1322602539-27004-4-git-send-email-emunson@mgebm.net>

On Tue, 2011-11-29 at 16:35 -0500, 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> 

Can it be documented in api.txt as well?

-- 

Sasha.

  reply	other threads:[~2011-12-03  9:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 21:35 [PATCH 0/5 V4] Avoid soft lockup message when KVM is stopped by host Eric B Munson
2011-11-29 21:35 ` [PATCH 1/5 V4] Add flag to indicate that a vm was stopped by the host Eric B Munson
2011-11-29 21:35 ` [PATCH 2/5 V4] Add functions to check if the host has stopped the vm Eric B Munson
2011-11-29 21:35 ` [PATCH 3/5 V4] Add ioctl for KVM_GUEST_STOPPED Eric B Munson
2011-12-03  9:16   ` Sasha Levin [this message]
2011-12-05 18:00     ` Eric B Munson
2011-11-29 21:35 ` [PATCH 4/5 V4] Add generic stubs for kvm stop check functions Eric B Munson
2011-11-29 21:35 ` [PATCH 5/5 V4] Add check for suspended vm in softlockup detector Eric B Munson
2011-12-01 21:25 ` [PATCH 0/5 V4] Avoid soft lockup message when KVM is stopped by host 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=1322903774.3782.1.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=arnd@arndb.de \
    --cc=avi@redhat.com \
    --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.