All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: Eric Blake <eblake@redhat.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: [PATCH v2] deal with guest paniced event
Date: Wed, 07 Mar 2012 10:45:10 +0800	[thread overview]
Message-ID: <4F56CBB6.90100@cn.fujitsu.com> (raw)
In-Reply-To: <4F56CA9E.2040907@redhat.com>

At 03/07/2012 10:40 AM, Eric Blake Wrote:
> On 03/06/2012 06:58 PM, Wen Congyang wrote:
>> When the host knows the guest is paniced, it will set
>> exit_reason to KVM_EXIT_GUEST_PANICED. So if qemu receive
>> this exit_reason, we can send a event to tell management
>> application that the guest is paniced and set the guest
>> status to RUN_STATE_PANICED.
> 
> s/PANICED/PANICKED/ throughout your series, for the correct spelling of
> the past tense of panic.

Sorry for my bad english. I will update it.

Thanks
Wen Congyang

> 

WARNING: multiple messages have this Message-ID (diff)
From: Wen Congyang <wency@cn.fujitsu.com>
To: Eric Blake <eblake@redhat.com>
Cc: 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: Re: [Qemu-devel] [PATCH v2] deal with guest paniced event
Date: Wed, 07 Mar 2012 10:45:10 +0800	[thread overview]
Message-ID: <4F56CBB6.90100@cn.fujitsu.com> (raw)
In-Reply-To: <4F56CA9E.2040907@redhat.com>

At 03/07/2012 10:40 AM, Eric Blake Wrote:
> On 03/06/2012 06:58 PM, Wen Congyang wrote:
>> When the host knows the guest is paniced, it will set
>> exit_reason to KVM_EXIT_GUEST_PANICED. So if qemu receive
>> this exit_reason, we can send a event to tell management
>> application that the guest is paniced and set the guest
>> status to RUN_STATE_PANICED.
> 
> s/PANICED/PANICKED/ throughout your series, for the correct spelling of
> the past tense of panic.

Sorry for my bad english. I will update it.

Thanks
Wen Congyang

> 


WARNING: multiple messages have this Message-ID (diff)
From: Wen Congyang <wency@cn.fujitsu.com>
To: Eric Blake <eblake@redhat.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 v2] deal with guest paniced event
Date: Wed, 07 Mar 2012 10:45:10 +0800	[thread overview]
Message-ID: <4F56CBB6.90100@cn.fujitsu.com> (raw)
In-Reply-To: <4F56CA9E.2040907@redhat.com>

At 03/07/2012 10:40 AM, Eric Blake Wrote:
> On 03/06/2012 06:58 PM, Wen Congyang wrote:
>> When the host knows the guest is paniced, it will set
>> exit_reason to KVM_EXIT_GUEST_PANICED. So if qemu receive
>> this exit_reason, we can send a event to tell management
>> application that the guest is paniced and set the guest
>> status to RUN_STATE_PANICED.
> 
> s/PANICED/PANICKED/ throughout your series, for the correct spelling of
> the past tense of panic.

Sorry for my bad english. I will update it.

Thanks
Wen Congyang

> 

  reply	other threads:[~2012-03-07  2:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07  1:50 [PATCH 0/2 v2] kvm: notify host when guest paniced Wen Congyang
2012-03-07  1:50 ` [Qemu-devel] " Wen Congyang
2012-03-07  1:53 ` [PATCH 1/2 " Wen Congyang
2012-03-07  1:53   ` [Qemu-devel] " Wen Congyang
2012-03-07  1:56 ` [PATCH 2/2 v2] kvm: set exit_reason to KVM_EXIT_GUEST_PANICED " Wen Congyang
2012-03-07  1:56   ` [Qemu-devel] " Wen Congyang
2012-03-07  1:58 ` [PATCH v2] deal with guest paniced event Wen Congyang
2012-03-07  1:58   ` [Qemu-devel] " Wen Congyang
2012-03-07  2:40   ` Eric Blake
2012-03-07  2:40     ` [Qemu-devel] " Eric Blake
2012-03-07  2:40     ` Eric Blake
2012-03-07  2:45     ` Wen Congyang [this message]
2012-03-07  2:45       ` Wen Congyang
2012-03-07  2:45       ` Wen Congyang
2012-03-07  9:53   ` Jan Kiszka
2012-03-07  9:53     ` [Qemu-devel] " Jan Kiszka
2012-03-07 10:05     ` Wen Congyang
2012-03-07 10:05       ` [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=4F56CBB6.90100@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=avi@redhat.com \
    --cc=eblake@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 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.