From: Avi Kivity <avi@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: kvm list <kvm@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
linux-kernel@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] kvm: notify host when guest paniced
Date: Tue, 28 Feb 2012 13:23:18 +0200 [thread overview]
Message-ID: <4F4CB926.6050600@redhat.com> (raw)
In-Reply-To: <4F4AF1FB.6000903@cn.fujitsu.com>
On 02/27/2012 05:01 AM, Wen Congyang wrote:
> We can know the guest is paniced when the guest runs on xen.
> But we do not have such feature on kvm. This patch implemnts
> this feature, and the implementation is the same as xen:
> register panic notifier, and call hypercall when the guest
> is paniced.
What's the motivation for this? "Xen does this" is insufficient.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
kvm list <kvm@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] kvm: notify host when guest paniced
Date: Tue, 28 Feb 2012 13:23:18 +0200 [thread overview]
Message-ID: <4F4CB926.6050600@redhat.com> (raw)
In-Reply-To: <4F4AF1FB.6000903@cn.fujitsu.com>
On 02/27/2012 05:01 AM, Wen Congyang wrote:
> We can know the guest is paniced when the guest runs on xen.
> But we do not have such feature on kvm. This patch implemnts
> this feature, and the implementation is the same as xen:
> register panic notifier, and call hypercall when the guest
> is paniced.
What's the motivation for this? "Xen does this" is insufficient.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-02-28 11:23 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 3:01 [PATCH] kvm: notify host when guest paniced Wen Congyang
2012-02-27 3:01 ` [Qemu-devel] " Wen Congyang
2012-02-27 3:05 ` [PATCH]qemu: deal with guest paniced event Wen Congyang
2012-02-27 3:05 ` [Qemu-devel] " Wen Congyang
2012-02-27 8:59 ` Jan Kiszka
2012-02-27 8:59 ` [Qemu-devel] " Jan Kiszka
2012-02-27 8:59 ` Jan Kiszka
2012-03-01 16:51 ` [Qemu-devel] " Luiz Capitulino
2012-03-01 16:51 ` Luiz Capitulino
2012-03-02 0:40 ` Wen Congyang
2012-03-02 0:40 ` Wen Congyang
2012-02-27 15:08 ` [PATCH] kvm: notify host when guest paniced Jan Kiszka
2012-02-27 15:08 ` [Qemu-devel] " Jan Kiszka
2012-02-28 5:26 ` Wen Congyang
2012-02-28 5:26 ` [Qemu-devel] " Wen Congyang
2012-02-28 5:26 ` Wen Congyang
2012-02-28 8:07 ` Wen Congyang
2012-02-28 8:07 ` [Qemu-devel] " Wen Congyang
2012-02-28 8:23 ` Wen Congyang
2012-02-28 8:23 ` [Qemu-devel] " Wen Congyang
2012-02-28 9:34 ` Jan Kiszka
2012-02-28 9:34 ` [Qemu-devel] " Jan Kiszka
2012-02-28 9:34 ` Jan Kiszka
2012-02-28 9:42 ` Wen Congyang
2012-02-28 9:42 ` [Qemu-devel] " Wen Congyang
2012-02-28 10:19 ` Jan Kiszka
2012-02-28 10:19 ` [Qemu-devel] " Jan Kiszka
2012-02-28 10:45 ` Gleb Natapov
2012-02-28 10:45 ` [Qemu-devel] " Gleb Natapov
2012-02-29 1:08 ` Wen Congyang
2012-02-29 1:08 ` [Qemu-devel] " Wen Congyang
2012-02-29 9:36 ` Gleb Natapov
2012-02-29 9:36 ` [Qemu-devel] " Gleb Natapov
2012-02-29 10:06 ` Wen Congyang
2012-02-29 10:06 ` [Qemu-devel] " Wen Congyang
2012-02-28 11:23 ` Avi Kivity [this message]
2012-02-28 11:23 ` Avi Kivity
2012-02-29 1:29 ` Wen Congyang
2012-02-29 1:29 ` [Qemu-devel] " Wen Congyang
2012-02-29 1:29 ` Wen Congyang
2012-02-29 9:49 ` Avi Kivity
2012-02-29 9:49 ` [Qemu-devel] " Avi Kivity
2012-02-29 9:55 ` Gleb Natapov
2012-02-29 9:55 ` [Qemu-devel] " Gleb Natapov
2012-02-29 10:00 ` Avi Kivity
2012-02-29 10:00 ` [Qemu-devel] " Avi Kivity
2012-02-29 10:00 ` Avi Kivity
2012-02-29 10:05 ` Gleb Natapov
2012-02-29 10:05 ` [Qemu-devel] " Gleb Natapov
2012-02-29 10:08 ` Avi Kivity
2012-02-29 10:08 ` [Qemu-devel] " Avi Kivity
2012-02-29 10:17 ` Wen Congyang
2012-02-29 10:17 ` [Qemu-devel] " Wen Congyang
2012-02-29 10:39 ` Avi Kivity
2012-02-29 10:39 ` [Qemu-devel] " Avi Kivity
2012-03-01 3:34 ` Wen Congyang
2012-03-01 3:34 ` [Qemu-devel] " Wen Congyang
2012-03-01 3:34 ` Wen Congyang
2012-03-01 5:21 ` Wen Congyang
2012-03-01 5:21 ` [Qemu-devel] " Wen Congyang
2012-02-29 10:44 ` Gleb Natapov
2012-02-29 10:44 ` [Qemu-devel] " Gleb Natapov
2012-02-29 10:48 ` Avi Kivity
2012-02-29 10:48 ` [Qemu-devel] " Avi Kivity
2012-02-29 10:52 ` Gleb Natapov
2012-02-29 10:52 ` [Qemu-devel] " Gleb Natapov
2012-02-29 9:58 ` Daniel P. Berrange
2012-02-29 9:58 ` [Qemu-devel] " Daniel P. Berrange
2012-02-29 10:05 ` Avi Kivity
2012-02-29 10:05 ` [Qemu-devel] " Avi Kivity
2012-02-29 10:19 ` Daniel P. Berrange
2012-02-29 10:19 ` [Qemu-devel] " Daniel P. Berrange
2012-02-29 10:44 ` Avi Kivity
2012-02-29 10:44 ` [Qemu-devel] " Avi Kivity
2012-02-29 10:31 ` Wen Congyang
2012-02-29 10:31 ` [Qemu-devel] " Wen Congyang
2012-02-29 10:31 ` Wen Congyang
2012-02-29 10:46 ` Avi Kivity
2012-02-29 10:46 ` [Qemu-devel] " Avi Kivity
2012-02-29 10:46 ` 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=4F4CB926.6050600@redhat.com \
--to=avi@redhat.com \
--cc=berrange@redhat.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 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.