From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7o1o-0001bI-0n for qemu-devel@nongnu.org; Wed, 14 Mar 2012 09:14:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7o1O-0002JR-3H for qemu-devel@nongnu.org; Wed, 14 Mar 2012 09:14:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:64523) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7o1N-0002JE-RZ for qemu-devel@nongnu.org; Wed, 14 Mar 2012 09:13:42 -0400 Message-ID: <4F609978.1060000@redhat.com> Date: Wed, 14 Mar 2012 15:13:28 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4F5DBC26.7060204@cn.fujitsu.com> <4F5DD0FD.9070904@redhat.com> <20120313091843.GB3800@redhat.com> <4F5F25BF.7060100@redhat.com> <4F6056FE.3020202@cn.fujitsu.com> <4F6063C8.8010005@redhat.com> <4F606A7C.9090900@cn.fujitsu.com> <4F606DCC.3020908@redhat.com> <4F60726E.3090807@cn.fujitsu.com> <4F607325.6050607@redhat.com> <20120314104608.GU2304@redhat.com> <4F607789.4010109@redhat.com> <4F607CE4.2060809@cn.fujitsu.com> <4F609822.7050502@redhat.com> In-Reply-To: <4F609822.7050502@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/2 v3] kvm: notify host when guest panicked List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wen Congyang Cc: Gleb Natapov , kvm list , Jan Kiszka , "linux-kernel@vger.kernel.org" , qemu-devel , Amit Shah , KAMEZAWA Hiroyuki On 03/14/2012 03:07 PM, Avi Kivity wrote: > On 03/14/2012 01:11 PM, Wen Congyang wrote: > > > > > > I don't think we want to use the driver. Instead, have a small piece of > > > code that resets the device and pushes out a string (the panic message?) > > > without any interrupts etc. > > > > > > It's still going to be less reliable than a hypercall, I agree. > > > > Do you still want to use complicated and less reliable way? > > Are you willing to try it out and see how complicated it really is? > > While it's more complicated, it's also more flexible. You can > communicate the panic message, whether the guest is attempting a kdump > and its own recovery or whether it wants the host to do it, etc., you > can communicate less severe failures like oopses. Note, this is similar to how network drivers have a special path (no interrupts) for netconsole output, this is used during panic as well. -- error compiling committee.c: too many arguments to function