From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40768) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKQ4F-0002X8-En for qemu-devel@nongnu.org; Tue, 26 Mar 2013 05:21:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UKQ49-0006rH-U8 for qemu-devel@nongnu.org; Tue, 26 Mar 2013 05:21:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60777) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKQ49-0006r6-L5 for qemu-devel@nongnu.org; Tue, 26 Mar 2013 05:21:13 -0400 Message-ID: <51516883.5050000@redhat.com> Date: Tue, 26 Mar 2013 10:21:07 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <514ACF4E.6030505@redhat.com> <1364267011-31975-1-git-send-email-hutao@cn.fujitsu.com> In-Reply-To: <1364267011-31975-1-git-send-email-hutao@cn.fujitsu.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v15.1 4/6] pvpanic: add document of pvpanic List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hu Tao Cc: qemu-devel Il 26/03/2013 04:03, Hu Tao ha scritto: > Signed-off-by: Hu Tao > --- > docs/specs/pvpanic.txt | 35 +++++++++++++++++++++++++++++++++++ > 1 file changed, 35 insertions(+) > create mode 100644 docs/specs/pvpanic.txt > > diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt > new file mode 100644 > index 0000000..1f14063 > --- /dev/null > +++ b/docs/specs/pvpanic.txt > @@ -0,0 +1,35 @@ > +PVPANIC DEVICE > +============== > + > +pvpanic device is a simulated ISA device, through which a guest panic > +event is sent to qemu, and a QMP event is generated. This allows > +management apps (e.g. libvirt) to be notified and respond to the event. > + > +The management app has the option of waiting for GUEST_PANICKED events, > +and/or polling for guest-panicked RunState, to learn when the pvpanic > +device has fired a panic event. > + > +ISA Interface > +------------- > + > +pvpanic uses port 0x505 to receive a panic event from the guest. On > +written, bit 0 is set to indicate guest panic has happened. On read, bit > +0 is set to indicate guest panic notification is supported. > + > +ACPI Interface > +-------------- > + > +pvpanic device is defined with ACPI ID "QEMU0001". Custom methods: > + > +RDPT: To determine whether guest panic notification is supported. > +Rrguments: None > +Return: Returns a byte, bit 0 set to indicate guest panic > + notification is supported. > + > +WRPT: To send a guest panic event > +Arguments: Arg0 is a byte, with bit 0 set to indicate guest panic has > + happened. > +Return: None > + > +The ACPI device will automatically refer to the right port in case it > +is modified. > Looks good. Paolo