qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Mihai Carabas <mihai.carabas@oracle.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, kraxel@redhat.com
Subject: Re: [PATCH 3/4] pvpanic : update pvpanic spec document
Date: Mon, 18 Jan 2021 11:32:06 +0100	[thread overview]
Message-ID: <605edf10-933f-db84-714b-b1a7ec9336a3@redhat.com> (raw)
In-Reply-To: <1610735646-13313-4-git-send-email-mihai.carabas@oracle.com>

On 1/15/21 7:34 PM, Mihai Carabas wrote:
> Add pvpanic PCI device support details in docs/specs/pvpanic.txt.
> 
> Signed-off-by: Mihai Carabas <mihai.carabas@oracle.com>
> ---
>  docs/specs/pvpanic.txt | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt
> index a90fbca..974aafd 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 as a
> +PCI device.
> +
>  ISA Interface
>  -------------
>  
> @@ -24,6 +27,14 @@ 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, 1 byte long. Any machine with a PCI device

"device" -> "bus"?

> +can enable a pvpanic device by adding '-device pvpanic-pci' to the command
> +line.
> +
>  ACPI Interface
>  --------------
>  
> 



  reply	other threads:[~2021-01-18 10:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 18:34 [PATCH v3] Add support for pvpanic pci device Mihai Carabas
2021-01-15 18:34 ` [PATCH 1/4] hw/misc/pvpanic: split-out generic and bus dependent code Mihai Carabas
2021-01-19 13:12   ` Peter Maydell
2021-01-15 18:34 ` [PATCH 2/4] hw/misc/pvpanic: add PCI interface support Mihai Carabas
2021-01-18 10:00   ` Gerd Hoffmann
2021-01-19 13:14   ` Peter Maydell
2021-01-20 11:57   ` Yan Vugenfirer
2021-01-20 12:49     ` Mihai Carabas
2021-01-20 13:43     ` Gerd Hoffmann
2021-01-20 14:05       ` Mihai Carabas
2021-01-15 18:34 ` [PATCH 3/4] pvpanic : update pvpanic spec document Mihai Carabas
2021-01-18 10:32   ` Philippe Mathieu-Daudé [this message]
2021-01-18 14:36     ` Mihai Carabas
2021-01-19 13:17   ` Peter Maydell
2021-01-15 18:34 ` [PATCH 4/4] tests/qtest: add a test case for pvpanic-pci Mihai Carabas
2021-01-18  7:42   ` Thomas Huth
2021-01-19 13:16   ` Peter Maydell
2021-01-19 13:29 ` [PATCH v3] Add support for pvpanic pci device Peter Maydell
2021-01-19 15:44   ` Peter Maydell

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=605edf10-933f-db84-714b-b1a7ec9336a3@redhat.com \
    --to=philmd@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mihai.carabas@oracle.com \
    --cc=peter.maydell@linaro.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).