From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Daniel Gollub <gollub@b1-systems.de>,
"Daniel P. Berrange" <berrange@redhat.com>,
kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 0/2] Introduce panic hypercall
Date: Tue, 21 Jun 2011 11:09:21 +0300 [thread overview]
Message-ID: <4E0051B1.8060801@redhat.com> (raw)
In-Reply-To: <20110621060251.GB491@redhat.com>
On 06/21/2011 09:02 AM, Gleb Natapov wrote:
> On Mon, Jun 20, 2011 at 07:34:57PM +0300, Avi Kivity wrote:
> > >The only two things which came to my mind are:
> > >
> > > * NMI (aka. ipmitool diag) - already available in qemu/kvm - but requires
> > > in-guest kexec/kdump
> > > * Hardware-Watchdog (also available in qemu/libvirt)
> >
> > A watchdog has the advantage that is also detects lockups.
> >
> And has disadvantage that all time base heuristics are bite us in the
> end.
The perf-based watchdog counts clocks-not-halted, not time, so it is
safe from time issues. We could make the hardware watchdog cheat in the
same way.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-21 8:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 13:38 [PATCH 0/2] Introduce panic hypercall Daniel Gollub
2011-06-20 13:38 ` [PATCH 1/2] Inroduce panic hypercall KVM_HC_PANIC (host) Daniel Gollub
2011-06-20 13:38 ` [PATCH 2/2] Call KVM_HC_PANIC if guest panics Daniel Gollub
2011-06-20 15:31 ` [PATCH 0/2] Introduce panic hypercall Avi Kivity
2011-06-20 15:38 ` Daniel P. Berrange
2011-06-20 15:45 ` Avi Kivity
2011-06-20 15:59 ` Jan Kiszka
2011-06-20 16:26 ` Daniel Gollub
2011-06-20 16:34 ` Avi Kivity
2011-06-20 17:13 ` Jan Kiszka
2011-06-20 17:23 ` Avi Kivity
2011-06-21 6:04 ` Gleb Natapov
2011-06-21 6:02 ` Gleb Natapov
2011-06-21 8:09 ` Avi Kivity [this message]
2011-06-21 8:41 ` Gleb Natapov
2011-06-21 8:56 ` Avi Kivity
2011-06-21 9:03 ` Gleb Natapov
2011-06-21 9:07 ` Avi Kivity
2011-06-21 9:30 ` shawn che
2011-06-20 19:28 ` Anthony Liguori
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=4E0051B1.8060801@redhat.com \
--to=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gleb@redhat.com \
--cc=gollub@b1-systems.de \
--cc=kvm@vger.kernel.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