From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH v2] deal with guest paniced event Date: Wed, 07 Mar 2012 10:45:10 +0800 Message-ID: <4F56CBB6.90100@cn.fujitsu.com> References: <4F56BEF2.4020405@cn.fujitsu.com> <4F56C0E1.1090703@cn.fujitsu.com> <4F56CA9E.2040907@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , kvm list , Jan Kiszka , qemu-devel , "linux-kernel@vger.kernel.org" , Avi Kivity , KAMEZAWA Hiroyuki To: Eric Blake Return-path: In-Reply-To: <4F56CA9E.2040907@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759043Ab2CGDAb (ORCPT ); Tue, 6 Mar 2012 22:00:31 -0500 Received: from cn.fujitsu.com ([222.73.24.84]:47409 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1756144Ab2CGDA3 (ORCPT ); Tue, 6 Mar 2012 22:00:29 -0500 X-IronPort-AV: E=Sophos;i="4.73,543,1325433600"; d="scan'208";a="4476387" Message-ID: <4F56CBB6.90100@cn.fujitsu.com> Date: Wed, 07 Mar 2012 10:45:10 +0800 From: Wen Congyang User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100413 Fedora/3.0.4-2.fc13 Thunderbird/3.0.4 MIME-Version: 1.0 To: Eric Blake CC: kvm list , qemu-devel , "linux-kernel@vger.kernel.org" , Avi Kivity , "Daniel P. Berrange" , KAMEZAWA Hiroyuki , Jan Kiszka , Gleb Natapov Subject: Re: [Qemu-devel] [PATCH v2] deal with guest paniced event References: <4F56BEF2.4020405@cn.fujitsu.com> <4F56C0E1.1090703@cn.fujitsu.com> <4F56CA9E.2040907@redhat.com> In-Reply-To: <4F56CA9E.2040907@redhat.com> X-MIMETrack: Itemize by SMTP Server on mailserver/fnst(Release 8.5.1FP4|July 25, 2010) at 2012-03-07 10:41:32, Serialize by Router on mailserver/fnst(Release 8.5.1FP4|July 25, 2010) at 2012-03-07 10:41:38, Serialize complete at 2012-03-07 10:41:38 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S577C-0005gS-CT for qemu-devel@nongnu.org; Tue, 06 Mar 2012 22:00:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S577A-0002An-RS for qemu-devel@nongnu.org; Tue, 06 Mar 2012 22:00:33 -0500 Received: from [222.73.24.84] (port=6302 helo=song.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S577A-0002Ab-G7 for qemu-devel@nongnu.org; Tue, 06 Mar 2012 22:00:32 -0500 Message-ID: <4F56CBB6.90100@cn.fujitsu.com> Date: Wed, 07 Mar 2012 10:45:10 +0800 From: Wen Congyang MIME-Version: 1.0 References: <4F56BEF2.4020405@cn.fujitsu.com> <4F56C0E1.1090703@cn.fujitsu.com> <4F56CA9E.2040907@redhat.com> In-Reply-To: <4F56CA9E.2040907@redhat.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [PATCH v2] deal with guest paniced event List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Gleb Natapov , kvm list , Jan Kiszka , qemu-devel , "linux-kernel@vger.kernel.org" , Avi Kivity , KAMEZAWA Hiroyuki 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 >