From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v13 6/8] introduce a new qom device to deal with panicked event Date: Mon, 04 Mar 2013 11:21:11 +0100 Message-ID: <51347597.8070406@redhat.com> References: <5134730A.2050406@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Peter Maydell , Gleb Natapov , "Michael S. Tsirkin" , Hu Tao , qemu-devel , Luiz Capitulino , Blue Swirl , Orit Wasserman , kvm list , Juan Quintela , Markus Armbruster , Jens Freimann , Jan Kiszka , Andrew Jones , Viktor Mihajlovski , Alex Williamson , Sasha Levin , Stefan Hajnoczi , KAMEZAWA Hiroyuki , Kevin Wolf , Alexander Graf , Anthony Liguori , Marcelo Tosatti Return-path: In-Reply-To: <5134730A.2050406@de.ibm.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 Il 04/03/2013 11:10, Christian Borntraeger ha scritto: > + //disabled wait: we either > + //do a > + //monitor_protocol_event(QEVENT_GUEST_PANICKED, whatever); > + //or > + //or call into pvevent > r = EXCP_HALTED; > break; > case ICPT_CPU_STOP: > > > I would prefer to just use the monitor_protocol_event, on the other hand > a call into pvent could make it configurable. I asked in my review to make pvevent not configurable, So monitor_protocol_event(QEVENT_GUEST_PANICKED); vm_stop(RUNSTATE_GUEST_PANICKED); would do I guess. Feel free to submit a patch to qemu-devel. Hu, please take any patch that Christian submits and incorporate it in your series for future posting. Paolo