From: Peng Hao <peng.hao2@zte.com.cn>
To: peter.maydell@linaro.org, drjones@redhat.com, philmd@redhat.com
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Peng Hao <peng.hao2@zte.com.cn>
Subject: [Qemu-devel] [PATCH V7 6/6] pvpanic : update pvpanic document
Date: Fri, 16 Nov 2018 18:50:06 +0800 [thread overview]
Message-ID: <1542365406-81310-7-git-send-email-peng.hao2@zte.com.cn> (raw)
In-Reply-To: <1542365406-81310-1-git-send-email-peng.hao2@zte.com.cn>
Add mmio support info in docs/specs/pvpanic.txt.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
---
docs/specs/pvpanic.txt | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt
index c7bbacc..4e1f69d 100644
--- a/docs/specs/pvpanic.txt
+++ b/docs/specs/pvpanic.txt
@@ -1,7 +1,7 @@
PVPANIC DEVICE
==============
-pvpanic device is a simulated ISA device, through which a guest panic
+pvpanic device is a simulated 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.
@@ -9,6 +9,13 @@ 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.
+Some architectures do not support ioport, just like arm. So add mmio
+support.
+
+When pvpanic device is implemented as a ISA device, it supports IOPORT
+mode. If pvpanic device supports MMIO mode, it will be implemented as
+a SYSBUS device.
+
ISA Interface
-------------
@@ -19,6 +26,13 @@ Software should set only bits both itself and the device recognize.
Currently, only bit 0 is recognized, setting it indicates a guest panic
has happened.
+SYSBUS Interface
+--------------
+
+The SYSBUS interface is similar to the ISA interface except that it uses
+MMIO. Pvpanic exposes a address space region 0x09070000--0x09070001 in
+arm virt machine. Currently only the first byte is used.
+
ACPI Interface
--------------
--
1.8.3.1
next prev parent reply other threads:[~2018-11-16 2:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:50 [Qemu-devel] [PATCH V7 0/5] add pvpanic mmio support Peng Hao
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 1/6] hw/misc/pvpanic: Build the pvpanic device in $(common-obj) Peng Hao
2018-11-20 14:22 ` Peter Maydell
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 2/6] hw/misc/pvpanic: Cosmetic renaming Peng Hao
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 3/6] hw/misc/pvpanic: Add the MMIO interface Peng Hao
2018-11-20 14:29 ` Peter Maydell
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 4/6] hw/arm/virt: Use the pvpanic device Peng Hao
2018-11-16 3:29 ` [Qemu-devel] [Qemu-arm] " Shannon Zhao
2018-11-16 4:31 ` peng.hao2
2018-11-20 14:32 ` [Qemu-devel] " Peter Maydell
2018-11-21 8:00 ` peng.hao2
2018-11-16 10:50 ` [Qemu-devel] [PATCH V7 5/6] hw/arm/virt: add pvpanic device in virt acpi table Peng Hao
2018-11-16 10:50 ` Peng Hao [this message]
2018-11-16 9:29 ` [Qemu-devel] [PATCH V7 6/6] pvpanic : update pvpanic document Andrew Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1542365406-81310-7-git-send-email-peng.hao2@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).