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 4/7 v6] add a new qevent: QEVENT_GUEST_PANICKED Date: Fri, 06 Jul 2012 17:40:18 +0800 [thread overview] Message-ID: <4FF6B282.8020607@cn.fujitsu.com> (raw) In-Reply-To: <4FF6B188.2060607@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 f6107ba..28f7482 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
WARNING: multiple messages have this Message-ID (diff)
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: [Qemu-devel] [PATCH 4/7 v6] add a new qevent: QEVENT_GUEST_PANICKED Date: Fri, 06 Jul 2012 17:40:18 +0800 [thread overview] Message-ID: <4FF6B282.8020607@cn.fujitsu.com> (raw) In-Reply-To: <4FF6B188.2060607@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 f6107ba..28f7482 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-07-06 9:35 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-06 9:36 [PATCH v6] kvm: notify host when the guest is panicked Wen Congyang 2012-07-06 9:36 ` [Qemu-devel] " Wen Congyang 2012-07-06 9:38 ` [PATCH 1/7 v6] start vm after reseting it Wen Congyang 2012-07-06 9:38 ` [Qemu-devel] " Wen Congyang 2012-07-06 9:38 ` [PATCH 2/7 v6] update linux headers Wen Congyang 2012-07-06 9:38 ` [Qemu-devel] " Wen Congyang 2012-07-06 10:25 ` Jan Kiszka 2012-07-06 10:25 ` [Qemu-devel] " Jan Kiszka 2012-07-06 10:50 ` Wen Congyang 2012-07-06 10:50 ` [Qemu-devel] " Wen Congyang 2012-07-06 10:50 ` Wen Congyang 2012-07-06 10:55 ` [Qemu-devel] " 陳韋任 (Wei-Ren Chen) 2012-07-06 10:55 ` 陳韋任 (Wei-Ren Chen) 2012-07-06 11:16 ` Jan Kiszka 2012-07-06 11:16 ` [Qemu-devel] " Jan Kiszka 2012-07-07 14:35 ` Paul Gortmaker 2012-07-07 14:35 ` [Qemu-devel] " Paul Gortmaker 2012-07-06 9:39 ` [PATCH 3/7 v6] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang 2012-07-06 9:39 ` [Qemu-devel] " Wen Congyang 2012-07-06 9:40 ` Wen Congyang [this message] 2012-07-06 9:40 ` [Qemu-devel] [PATCH 4/7 v6] add a new qevent: QEVENT_GUEST_PANICKED Wen Congyang 2012-07-06 9:41 ` [PATCH 5/7 v6] introduce a new qom device to deal with panicked event Wen Congyang 2012-07-06 9:41 ` [Qemu-devel] " Wen Congyang 2012-07-06 11:05 ` Jan Kiszka 2012-07-06 11:05 ` [Qemu-devel] " Jan Kiszka 2012-07-06 11:05 ` Jan Kiszka 2012-07-18 1:54 ` Wen Congyang 2012-07-18 1:54 ` [Qemu-devel] " Wen Congyang 2012-07-18 9:19 ` Jan Kiszka 2012-07-18 9:19 ` [Qemu-devel] " Jan Kiszka 2012-07-18 9:25 ` Jan Kiszka 2012-07-18 9:25 ` [Qemu-devel] " Jan Kiszka 2012-07-06 9:41 ` [PATCH 6/7 v6] deal with guest panicked event accoring to -onpanic parameter Wen Congyang 2012-07-06 9:41 ` [Qemu-devel] " Wen Congyang 2012-07-06 11:12 ` Jan Kiszka 2012-07-06 11:12 ` [Qemu-devel] " Jan Kiszka 2012-07-06 11:12 ` Jan Kiszka 2012-07-06 9:41 ` [PATCH 7/7 v6] deal with panicked event accoring to '-machine panic_action=action' Wen Congyang 2012-07-06 9:41 ` [Qemu-devel] " Wen Congyang 2012-07-06 11:09 ` Jan Kiszka 2012-07-06 11:09 ` [Qemu-devel] " Jan Kiszka 2012-07-06 11:09 ` Jan Kiszka 2012-07-09 10:44 ` Wen Congyang 2012-07-09 10:44 ` [Qemu-devel] " Wen Congyang
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=4FF6B282.8020607@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: linkBe 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.