From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: pkrempa@redhat.com, mst@redhat.com, libvir-list@redhat.com,
marcel.a@redhat.com, qemu-devel@nongnu.org, rhod@redhat.com,
Anthony Liguori <anthony@codemonkey.ws>,
Laszlo Ersek <lersek@redhat.com>,
afaerber@suse.de
Subject: Re: [Qemu-devel] [libvirt] pvpanic plans?
Date: Tue, 27 Aug 2013 14:13:34 +0100 [thread overview]
Message-ID: <20130827131334.GT613@redhat.com> (raw)
In-Reply-To: <521663A9.6040207@redhat.com>
On Thu, Aug 22, 2013 at 09:16:57PM +0200, Paolo Bonzini wrote:
> Il 22/08/2013 19:53, Laszlo Ersek ha scritto:
> >> > We should just introduce a simple watchdog device based on virtio and
> >> > call it a day. Then it's cross platform, solves the guest enumeration
> >> > problem, and libvirt can detect the presence of the new device.
> > If the guest doesn't initialize the proposed virtio-panic device, then
> > it will lie dormant too, just like the current pvpanic device. That's good.
> >
> > However a new (standalone) virtio device will take up yet another PCI
> > function (a full device if you want it to be hotpluggable). PCI
> > functions are scarcer than ioports.
>
> Not just that. Panic notifiers are called in a substantially unknown
> environment, with locks taken or interrupts already set up.
>
> This is why we went for a simple ISA device. Configuration via ACPI
> follows naturally from there, and anyway any other standard of the day
> would have had the same problem with Windows. At some point we had ACPI
> methods instead of a simple ioport write, but we had to remove that
> because the ACPI subsystem might have had its lock taken.
>
> Also, a virtio watchdog device makes little sense, IMHO. PV makes sense
> if emulation has insufficient performance, excessive CPU usage, or
> excessive complexity. We already have both an ISA and a PCI watchdog,
> and they serve their purpose wonderfully.
I also don't think that panic notifiers & watchdogs are really
serving the same purpose. The panic notifier is an alert to a
specific known kernel crash. A watchdog is merely a timeout,
which is inferred to mean /something/ went wrong. Both have
their uses IMHO & we should not conflate the two.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2013-08-27 13:13 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 16:10 [Qemu-devel] pvpanic plans? Paolo Bonzini
2013-08-22 16:44 ` Anthony Liguori
2013-08-22 17:53 ` Laszlo Ersek
2013-08-22 18:25 ` Anthony Liguori
2013-08-27 8:42 ` Richard W.M. Jones
2013-08-22 19:16 ` Paolo Bonzini
2013-08-22 20:09 ` Anthony Liguori
2013-08-22 20:36 ` Laszlo Ersek
2013-08-22 20:39 ` Anthony Liguori
2013-08-23 8:52 ` Paolo Bonzini
2013-08-22 21:08 ` Peter Maydell
2013-08-27 8:06 ` Richard W.M. Jones
2013-08-27 13:08 ` Ronen Hod
2013-08-27 13:20 ` Richard W.M. Jones
2013-08-27 13:26 ` Anthony Liguori
2013-08-27 13:57 ` Richard W.M. Jones
2013-08-27 13:13 ` Daniel P. Berrange [this message]
2013-08-27 13:17 ` [Qemu-devel] [libvirt] " Anthony Liguori
2013-08-27 13:21 ` Richard W.M. Jones
2013-08-22 17:15 ` [Qemu-devel] " Laszlo Ersek
2013-08-22 18:33 ` Anthony Liguori
2013-08-22 19:44 ` Christian Borntraeger
2013-08-22 19:19 ` Paolo Bonzini
2013-08-22 19:41 ` Laszlo Ersek
2013-08-22 20:02 ` [Qemu-devel] [libvirt] " Eric Blake
2013-10-24 2:39 ` [Qemu-devel] " Hu Tao
2013-10-29 16:01 ` Markus Armbruster
2013-10-31 14:30 ` Michael S. Tsirkin
2013-10-31 14:32 ` Eric Blake
2013-10-31 14:34 ` Anthony Liguori
2013-10-31 14:39 ` Paolo Bonzini
2013-10-31 14:52 ` Michael S. Tsirkin
2013-10-31 14:56 ` Paolo Bonzini
2013-10-31 15:09 ` Michael S. Tsirkin
2013-10-31 15:26 ` Paolo Bonzini
2013-10-31 15:45 ` Michael S. Tsirkin
2013-10-31 15:56 ` Paolo Bonzini
2013-10-31 16:14 ` Michael S. Tsirkin
2013-10-31 16:17 ` Paolo Bonzini
2013-10-31 16:26 ` Michael S. Tsirkin
2013-10-31 16:38 ` Paolo Bonzini
2013-10-31 16:48 ` Michael S. Tsirkin
2013-10-31 16:52 ` Paolo Bonzini
2013-10-31 17:00 ` Michael S. Tsirkin
2013-10-31 17:09 ` Paolo Bonzini
2013-10-31 17:01 ` Michael S. Tsirkin
2013-10-31 17:10 ` Paolo Bonzini
2013-10-31 17:18 ` Michael S. Tsirkin
2013-10-31 18:03 ` Paolo Bonzini
2013-10-31 16:28 ` Michael S. Tsirkin
2013-10-31 14:47 ` Michael S. Tsirkin
2013-10-31 14:49 ` Eric Blake
2013-10-31 15:07 ` Michael S. Tsirkin
2013-11-04 9:25 ` Christian Borntraeger
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=20130827131334.GT613@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=lersek@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rhod@redhat.com \
/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).