From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Andrew Jones" <drjones@redhat.com>,
"Peng Hao" <peng.hao2@zte.com.cn>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH V11 0/8] add pvpanic mmio support
Date: Tue, 4 Dec 2018 13:48:30 +0000 [thread overview]
Message-ID: <20181204134830.GB17825@redhat.com> (raw)
In-Reply-To: <CAFEAcA_ovMgKPPjtYVASFqhzM7MX79EJYMZuFY4-FGRh4oqN8A@mail.gmail.com>
On Tue, Dec 04, 2018 at 12:59:51PM +0000, Peter Maydell wrote:
> On Tue, 4 Dec 2018 at 12:47, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > After it had merged there were some changes and the question of turning
> > it into a PCI device was raised. Paolo was concerned that the guest OS
> > is in an unknown state (arbitrary locks held, data structures corrupt,
> > etc) when panic is fired, so simplicity of the I/O port was desirable:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg03309.html
> >
> > Anthony countered that even a PCI device could simply do an outb() in
> > config space:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg03325.html
> >
> > So it is not clear using a PCI device is in fact a problem in terms of
> > reliability at time of firing.
>
> ...and if we'd done it that way in the first place for x86 then
> we wouldn't be having to do anything at all now for Arm.
> That suggests to me that we should do it that way now, and then we
> can avoid having to do a bunch of extra development work for the
> next architecture, or the next interesting Arm board model.
On s390 there's always a panic notifier mechanism as it is a
integral part of the architecture.
On PowerPC, pSeries guests have access to a panic notifier provided
by the firmware.
On x86, as well as pvpanic, there is also a paravirtualized
option defined by the HyperV extensions "hv_crash"
IIUC a PCI based solution would be usable on x86, s390, powerpc (pseries),
aarch64 (virt) and eventually riscv (virt). Of those, it is only
aarch64 and riscv that lack a panic notifier solution today.
I feel like we've already lost from the pov of a standardized solution,
but that doesn't mean we shouldn't still consider using PCI if it does
look like the best otion for arm/riscv.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Peng Hao" <peng.hao2@zte.com.cn>,
"Andrew Jones" <drjones@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH V11 0/8] add pvpanic mmio support
Date: Tue, 4 Dec 2018 13:48:30 +0000 [thread overview]
Message-ID: <20181204134830.GB17825@redhat.com> (raw)
In-Reply-To: <CAFEAcA_ovMgKPPjtYVASFqhzM7MX79EJYMZuFY4-FGRh4oqN8A@mail.gmail.com>
On Tue, Dec 04, 2018 at 12:59:51PM +0000, Peter Maydell wrote:
> On Tue, 4 Dec 2018 at 12:47, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > After it had merged there were some changes and the question of turning
> > it into a PCI device was raised. Paolo was concerned that the guest OS
> > is in an unknown state (arbitrary locks held, data structures corrupt,
> > etc) when panic is fired, so simplicity of the I/O port was desirable:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg03309.html
> >
> > Anthony countered that even a PCI device could simply do an outb() in
> > config space:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg03325.html
> >
> > So it is not clear using a PCI device is in fact a problem in terms of
> > reliability at time of firing.
>
> ...and if we'd done it that way in the first place for x86 then
> we wouldn't be having to do anything at all now for Arm.
> That suggests to me that we should do it that way now, and then we
> can avoid having to do a bunch of extra development work for the
> next architecture, or the next interesting Arm board model.
On s390 there's always a panic notifier mechanism as it is a
integral part of the architecture.
On PowerPC, pSeries guests have access to a panic notifier provided
by the firmware.
On x86, as well as pvpanic, there is also a paravirtualized
option defined by the HyperV extensions "hv_crash"
IIUC a PCI based solution would be usable on x86, s390, powerpc (pseries),
aarch64 (virt) and eventually riscv (virt). Of those, it is only
aarch64 and riscv that lack a panic notifier solution today.
I feel like we've already lost from the pov of a standardized solution,
but that doesn't mean we shouldn't still consider using PCI if it does
look like the best otion for arm/riscv.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-12-04 13:49 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 19:26 [Qemu-arm] [PATCH V11 0/8] add pvpanic mmio support Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 18:50 ` [Qemu-arm] " Peter Maydell
2018-12-03 18:50 ` [Qemu-devel] " Peter Maydell
2018-12-04 0:41 ` [Qemu-arm] " peng.hao2
2018-12-04 0:41 ` [Qemu-devel] " peng.hao2
2018-12-04 9:40 ` [Qemu-arm] " Peter Maydell
2018-12-04 9:40 ` [Qemu-devel] " Peter Maydell
2018-12-04 12:05 ` Andrew Jones
2018-12-04 12:05 ` Andrew Jones
2018-12-04 12:48 ` Peter Maydell
2018-12-04 12:48 ` Peter Maydell
2018-12-05 0:27 ` [Qemu-arm] " peng.hao2
2018-12-05 0:27 ` [Qemu-devel] " peng.hao2
2018-12-05 14:54 ` [Qemu-arm] " Peter Maydell
2018-12-05 14:54 ` [Qemu-devel] " Peter Maydell
2018-12-06 2:02 ` peng.hao2
2018-12-06 2:02 ` [Qemu-devel] " peng.hao2
2018-12-04 12:47 ` [Qemu-arm] [Qemu-devel] " Daniel P. Berrangé
2018-12-04 12:47 ` Daniel P. Berrangé
2018-12-04 12:59 ` [Qemu-arm] " Peter Maydell
2018-12-04 12:59 ` Peter Maydell
2018-12-04 13:30 ` [Qemu-arm] " Paolo Bonzini
2018-12-04 13:30 ` Paolo Bonzini
2018-12-04 13:43 ` [Qemu-arm] " Peter Maydell
2018-12-04 13:43 ` Peter Maydell
2018-12-04 13:53 ` Paolo Bonzini
2018-12-04 13:53 ` Paolo Bonzini
2018-12-04 19:10 ` [Qemu-arm] " Michael S. Tsirkin
2018-12-04 19:10 ` [Qemu-devel] " Michael S. Tsirkin
2018-12-04 13:48 ` Daniel P. Berrangé [this message]
2018-12-04 13:48 ` Daniel P. Berrangé
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 1/8] hw/misc/pvpanic: Build the pvpanic device in $(common-obj) Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 2/8] hw/misc/pvpanic: Cosmetic renaming Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 3/8] hw/misc/pvpanic: Add the MMIO interface Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 4/8] hw/arm/virt: Use the pvpanic device Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 11:21 ` [Qemu-arm] " Andrew Jones
2018-12-03 11:21 ` [Qemu-devel] " Andrew Jones
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 5/8] hw/arm/virt: add pvpanic device in virt acpi table Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 6/8] hw/arm/virt: add configure interface for pvpanic-mmio Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 11:18 ` [Qemu-arm] " Andrew Jones
2018-12-03 11:18 ` [Qemu-devel] " Andrew Jones
2018-12-03 11:22 ` [Qemu-arm] " Andrew Jones
2018-12-03 11:22 ` [Qemu-devel] " Andrew Jones
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 7/8] hw/arm/virt: use the configure interface Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
2018-12-03 19:26 ` [Qemu-arm] [PATCH V11 8/8] pvpanic : update pvpanic document Peng Hao
2018-12-03 19:26 ` [Qemu-devel] " Peng Hao
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=20181204134830.GB17825@redhat.com \
--to=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=peng.hao2@zte.com.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.