qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Mihai Carabas <mihai.carabas@oracle.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: pvpanic mmio support
Date: Tue, 13 Oct 2020 21:53:22 +0100	[thread overview]
Message-ID: <CAFEAcA-At8-thXWBN-JanPhcgzCg==hhYWthGxOZF-82dMDCcA@mail.gmail.com> (raw)
In-Reply-To: <a6600c8b-74d9-4c1a-73d9-6302461b7192@oracle.com>

On Tue, 13 Oct 2020 at 21:37, Mihai Carabas <mihai.carabas@oracle.com> wrote:
> Does anyone know if there is any progress with pvpanic patches that
> brings in mmio support [1]?

I don't think so. If I recall correctly there was quite a lot
of discussion on at least one version of that patchset, and it
was never clear to me at least that having an MMIO pvpanic device
was actually useful (as opposed to for instance having a PCI
device, or maybe a virtio backend, both of which have the
virtue of being (a) pluggable by the user and (b) autodetectable
by the guest).

> I see no activity since late 2018, but I do
> see support added to the kernel (also asking myself how this was tested):
>
> 46f934c misc/pvpanic: add support to get pvpanic device info FDT
> b1d9d6c dt-bindings: misc/pvpanic: add document for pvpanic-mmio
> 725eba2 misc/pvpanic: add MMIO support

That was probably tested with somebody's not-actually-in-QEMU
patchset. The documentation in the kernel's
Documentation/devicetree/bindings/misc/pvpanic-mmio.txt
is just wrong when it says
# QEMU's emulation / virtualization targets provide the following
# PVPANIC MMIO Configuration interface on the "virt" machine.

because we definitely do not.

thanks
-- PMM


      reply	other threads:[~2020-10-13 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 17:37 pvpanic mmio support Mihai Carabas
2020-10-13 20:53 ` Peter Maydell [this message]

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='CAFEAcA-At8-thXWBN-JanPhcgzCg==hhYWthGxOZF-82dMDCcA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=mihai.carabas@oracle.com \
    --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).