qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Daniel Gollub <gollub@b1-systems.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall
Date: Tue, 21 Jun 2011 09:02:51 +0300	[thread overview]
Message-ID: <20110621060251.GB491@redhat.com> (raw)
In-Reply-To: <4DFF76B1.8020509@redhat.com>

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.

--
			Gleb.

  parent reply	other threads:[~2011-06-21  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1308577094-17551-1-git-send-email-gollub@b1-systems.de>
     [not found] ` <4DFF67CB.3060807@redhat.com>
     [not found]   ` <20110620153825.GH13042@redhat.com>
2011-06-20 15:45     ` [Qemu-devel] [PATCH 0/2] Introduce panic hypercall 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 [this message]
2011-06-21  8:09             ` Avi Kivity
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

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=20110621060251.GB491@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@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;
as well as URLs for NNTP newsgroup(s).