From: Wen Congyang <wency@cn.fujitsu.com>
To: kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Gleb Natapov <gleb@redhat.com>
Subject: [PATCH v8 4/6] add a new qevent: QEVENT_GUEST_PANICKED
Date: Wed, 08 Aug 2012 10:46:34 +0800 [thread overview]
Message-ID: <5021D30A.1090106@cn.fujitsu.com> (raw)
In-Reply-To: <5021D235.4050800@cn.fujitsu.com>
This event will be emited when the guest is panicked.
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
---
monitor.c | 1 +
monitor.h | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monitor.c
index 49dccfe..c892b7e 100644
--- a/monitor.c
+++ b/monitor.c
@@ -458,6 +458,7 @@ static const char *monitor_event_names[] = {
[QEVENT_SUSPEND] = "SUSPEND",
[QEVENT_WAKEUP] = "WAKEUP",
[QEVENT_BALLOON_CHANGE] = "BALLOON_CHANGE",
+ [QEVENT_GUEST_PANICKED] = "GUEST_PANICKED",
};
QEMU_BUILD_BUG_ON(ARRAY_SIZE(monitor_event_names) != QEVENT_MAX)
diff --git a/monitor.h b/monitor.h
index 5f4de1b..cb7de8c 100644
--- a/monitor.h
+++ b/monitor.h
@@ -42,6 +42,7 @@ typedef enum MonitorEvent {
QEVENT_SUSPEND,
QEVENT_WAKEUP,
QEVENT_BALLOON_CHANGE,
+ QEVENT_GUEST_PANICKED,
/* Add to 'monitor_event_names' array in monitor.c when
* defining new events here */
--
1.7.1
next prev parent reply other threads:[~2012-08-08 2:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 2:43 [PATCH v8] kvm: notify host when the guest is panicked Wen Congyang
2012-08-08 2:44 ` [PATCH v8 1/6] start vm after reseting it Wen Congyang
2012-08-08 2:45 ` [PATCH v8 2/6] kvm: Update kernel headers Wen Congyang
2012-08-08 2:45 ` [PATCH v8 3/6] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang
2012-08-08 2:46 ` Wen Congyang [this message]
2012-08-08 2:47 ` [PATCH v8 5/6] introduce a new qom device to deal with panicked event Wen Congyang
2012-08-08 19:01 ` [Qemu-devel] " Blue Swirl
2012-08-22 7:30 ` Wen Congyang
2012-08-25 7:36 ` Blue Swirl
2012-08-08 2:47 ` [PATCH v8 6/6] allower the user to disable pv event support Wen Congyang
2012-08-08 9:12 ` [PATCH v8] kvm: notify host when the guest is panicked Andrew Jones
2012-08-08 9:28 ` Wen Congyang
2012-08-13 18:21 ` Marcelo Tosatti
2012-08-13 19:48 ` [Qemu-devel] " 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 ` [Qemu-devel] " 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=5021D30A.1090106@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=avi@redhat.com \
--cc=berrange@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 \
/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).