From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53658) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULvhf-0008GH-UB for qemu-devel@nongnu.org; Sat, 30 Mar 2013 09:20:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULvhc-0002V2-KF for qemu-devel@nongnu.org; Sat, 30 Mar 2013 09:20:15 -0400 Received: from mail-ve0-f181.google.com ([209.85.128.181]:41271) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULvhc-0002Ut-Gc for qemu-devel@nongnu.org; Sat, 30 Mar 2013 09:20:12 -0400 Received: by mail-ve0-f181.google.com with SMTP id pa12so1268262veb.40 for ; Sat, 30 Mar 2013 06:20:12 -0700 (PDT) Date: Sat, 30 Mar 2013 09:20:09 -0400 From: Kevin O'Connor Message-ID: <20130330132009.GA12564@morn.localdomain> References: <1364545124-9781-1-git-send-email-hutao@cn.fujitsu.com> <20130329133310.GA9206@morn.localdomain> <51559BD8.5080502@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51559BD8.5080502@redhat.com> Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH v16] Add pvpanic device driver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Peter Maydell , Gleb Natapov , "Michael S. Tsirkin" , Hu Tao , seabios@seabios.org, qemu-devel , Markus Armbruster , Blue Swirl , Orit Wasserman , Juan Quintela , Alexander Graf , Christian Borntraeger , Jan Kiszka , Andrew Jones , Alex Williamson , Sasha Levin , Stefan Hajnoczi , Luiz Capitulino , KAMEZAWA Hiroyuki , Anthony Liguori , Marcelo Tosatti On Fri, Mar 29, 2013 at 02:49:12PM +0100, Paolo Bonzini wrote: > Il 29/03/2013 14:33, Kevin O'Connor ha scritto: > > On Fri, Mar 29, 2013 at 04:18:44PM +0800, Hu Tao wrote: > >> pvpanic device is used to notify host(qemu) when guest panic happens. > > > > Thanks. However, we're planning a move of ACPI tables from SeaBIOS to > > QEMU. I think this should wait until after the move. > > The device should be in QEMU 1.5, and the SSDT probably will still be in > SeaBIOS by then (and might even be the last to move, since it's quite > complex and dynamic). I don't think it is fair to block this patch on > those grounds... What is the user visible impact of not having a panic device? My main concern is that the patch creates a new fw_cfg channel between qemu and seabios thats sole purpose is to alter the OS visible ACPI tables. These types of QEMU->SeaBIOS interfaces are fragile and are (in sum) quite complex. -Kevin