qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mihai Carabas <mihai.carabas@oracle.com>
To: qemu-devel@nongnu.org
Cc: Mihai Carabas <mihai.carabas@oracle.com>,
	Peng Hao <peng.hao2@zte.com.cn>
Subject: [PATCH 5/6] pvpanic : update pvpanic document
Date: Wed, 28 Oct 2020 15:32:58 +0200	[thread overview]
Message-ID: <1603891979-11961-6-git-send-email-mihai.carabas@oracle.com> (raw)
In-Reply-To: <1603891979-11961-1-git-send-email-mihai.carabas@oracle.com>

From: Peng Hao <peng.hao2@zte.com.cn>

Add mmio mode as a pci device support info in docs/specs/pvpanic.txt.

Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
Signed-off-by: Mihai Carabas <mihai.carabas@oracle.com>
---
 docs/specs/pvpanic.txt | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt
index a90fbca..4258922 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,9 @@ 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.
 
+The pvpanic device can be implemented as an ISA device (using IOPORT),
+or, since qemu 4.0, as a PCI device.
+
 ISA Interface
 -------------
 
@@ -24,6 +27,13 @@ bit 1: a guest panic has happened and will be handled by the guest;
        the host should record it or report it, but should not affect
        the execution of the guest.
 
+PCI Interface
+-------------
+
+The PCI interface is similar to the ISA interface except that it uses an MMIO
+address space provided by its BAR0. For example, the arm virt machine may
+enable a pvpanic device by adding '-device pvpanic-pci' to the command line.
+
 ACPI Interface
 --------------
 
-- 
1.8.3.1



  parent reply	other threads:[~2020-10-28 14:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 13:32 [PATCH] Add support for pvpanic pci device Mihai Carabas
2020-10-28 13:32 ` [PATCH 1/6] hw/misc/pvpanic: Build the pvpanic device for any machine Mihai Carabas
2020-12-14 10:47   ` Peter Maydell
2020-12-14 10:54     ` Peter Maydell
2020-10-28 13:32 ` [PATCH 2/6] hw/misc/pvpanic: Cosmetic renaming Mihai Carabas
2020-12-14 10:20   ` Peter Maydell
2020-10-28 13:32 ` [PATCH 3/6] hw/misc/pvpanic: Add the PCI interface Mihai Carabas
2020-12-14 10:58   ` Peter Maydell
2020-10-28 13:32 ` [PATCH 4/6] hw/arm/virt: Use the pvpanic pci device Mihai Carabas
2020-12-14 10:24   ` Peter Maydell
2020-10-28 13:32 ` Mihai Carabas [this message]
2020-12-14 10:30   ` [PATCH 5/6] pvpanic : update pvpanic document Peter Maydell
2020-10-28 13:32 ` [PATCH 6/6] pvpanic: break dependency on ISA_BUS adding PCI Mihai Carabas
2020-10-29 12:30 ` [PATCH] Add support for pvpanic pci device Mihai Carabas
2020-11-23 13:42   ` Mihai Carabas
2020-12-14 11:03 ` Peter Maydell
2020-12-14 11:15   ` Mihai Carabas

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=1603891979-11961-6-git-send-email-mihai.carabas@oracle.com \
    --to=mihai.carabas@oracle.com \
    --cc=peng.hao2@zte.com.cn \
    --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).