From: Andrew Jones <drjones@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked
Date: Wed, 8 Aug 2012 11:12:36 +0200 [thread overview]
Message-ID: <20120808091235.GA2663@turtle.usersys.redhat.com> (raw)
In-Reply-To: <5021D235.4050800@cn.fujitsu.com>
On Wed, Aug 08, 2012 at 10:43:01AM +0800, Wen Congyang wrote:
> diff --git a/Documentation/virtual/kvm/pv_event.txt b/Documentation/virtual/kvm/pv_event.txt
> new file mode 100644
> index 0000000..0ebc890
> --- /dev/null
> +++ b/Documentation/virtual/kvm/pv_event.txt
> @@ -0,0 +1,32 @@
> +The KVM paravirtual event interface
> +=================================
> +
> +Initializing the paravirtual event interface
> +======================
> +kvm_pv_event_init()
> +Argiments:
> + None
> +
> +Return Value:
> + 0 : The guest kernel can't use paravirtual event interface.
> + -1: The guest kernel can use paravirtual event interface.
> +
This documentation has the can and can't backwards.
next prev parent reply other threads:[~2012-08-08 9:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 2:43 [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked Wen Congyang
2012-08-08 2:44 ` [Qemu-devel] [PATCH v8 1/6] start vm after reseting it Wen Congyang
2012-08-08 2:45 ` [Qemu-devel] [PATCH v8 2/6] kvm: Update kernel headers Wen Congyang
2012-08-08 2:45 ` [Qemu-devel] [PATCH v8 3/6] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang
2012-08-08 2:46 ` [Qemu-devel] [PATCH v8 4/6] add a new qevent: QEVENT_GUEST_PANICKED Wen Congyang
2012-08-08 2:47 ` [Qemu-devel] [PATCH v8 5/6] introduce a new qom device to deal with panicked event Wen Congyang
2012-08-08 19:01 ` Blue Swirl
2012-08-22 7:30 ` Wen Congyang
2012-08-25 7:36 ` Blue Swirl
2012-08-08 2:47 ` [Qemu-devel] [PATCH v8 6/6] allower the user to disable pv event support Wen Congyang
2012-08-08 9:12 ` Andrew Jones [this message]
2012-08-08 9:28 ` [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked Wen Congyang
2012-08-13 18:21 ` Marcelo Tosatti
2012-08-13 19:48 ` Eric Blake
2012-08-13 20:24 ` Marcelo Tosatti
2012-08-14 7:47 ` Gleb Natapov
2012-08-14 15:29 ` Marcelo Tosatti
2012-08-14 15:50 ` Gleb Natapov
2012-08-14 8:56 ` Daniel P. Berrange
2012-08-14 10:42 ` Jan Kiszka
2012-08-14 14:55 ` Yan Vugenfirer
2012-08-14 15:01 ` Jan Kiszka
2012-08-14 15:42 ` Marcelo Tosatti
2012-08-14 18:53 ` Anthony Liguori
2012-08-14 19:19 ` Marcelo Tosatti
2012-08-14 19:35 ` Anthony Liguori
2012-08-14 20:53 ` Marcelo Tosatti
2012-08-14 22:59 ` Anthony Liguori
2012-08-15 0:25 ` [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked\ Marcelo Tosatti
2012-08-22 6:33 ` [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked Wen Congyang
2012-08-15 9:56 ` Gleb Natapov
2012-08-15 11:42 ` Yan Vugenfirer
2012-08-15 11:38 ` Yan Vugenfirer
2012-08-14 19:58 ` Peter Maydell
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=20120808091235.GA2663@turtle.usersys.redhat.com \
--to=drjones@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).