All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: pkrempa@redhat.com, marcel.a@redhat.com, libvir-list@redhat.com,
	hutao@cn.fujitsu.com, mst@redhat.com, qemu-devel@nongnu.org,
	armbru@redhat.com, rhod@redhat.com, kraxel@redhat.com,
	anthony@codemonkey.ws, lcapitulino@redhat.com, lersek@redhat.com,
	afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess
Date: Wed, 21 Aug 2013 19:11:43 +0200	[thread overview]
Message-ID: <5214F4CF.1080908@redhat.com> (raw)
In-Reply-To: <5214F47A.2080706@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 21/08/2013 19:10, Eric Blake ha scritto:
> On 08/21/2013 10:56 AM, Paolo Bonzini wrote:
>>> eg it is valid to have <on_crash> present in the XML at all 
>>> times, even if there's no pvpanic device present. That simply 
>>> means the actions will never be triggered.
>> 
>> So are you suggesting to add a <pvpanic/> element to <devices>?
>> That may be fine, but it doesn't seem very user-friendly.
> 
> No less friendly than having a <memballoon> device, and certainly 
> automatable via libosinfo integration into virt-install.

Fair enough.  Still I'm not sure that a new <on_panic> element should
be ruled out, see my other message.

Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSFPTPAAoJEBvWZb6bTYby4bkP/RKM2mycCtwhdZIZLJU2fWCf
F7pcmD+uRqmBc5VtVh1K423ozo42lUcdb+erIzkIwH2sPVsiGNoue1IPRgHs1Azy
Fq06uESPTVAroudFsFAYj8XtG6rH4UqfKFeym4RK97fMH87FLjRLX8bzm1R/mdw8
WWJ1TIspJ0tJceSewRVO2F12OjKC5AIIA36BTUH85dR2P64mJX/aZvhkQzTUn4ii
Tp/+661RwyfRfgK2zY/gl6sh0qRp4i3Q3sdElKyPwDkFh6Z86XE6zTJTxJRMRfvl
tqVg5elZeNHkgoBtAr4azGpn1j+mxuJ0dNmLJLC1/tyGCZojzL9C4Cc/gflJLGSP
gW9VqBG7L8FRpwcCVdeoCMHFoZh2N39grAl7vkrqHf0zYR0oZidJ98MvCNwxZA4m
YCf8gFMLx0vkEwa8BB4YexMzn5DCbQmSOuoJSd7XX3lYlb6mJudkQh+d+OXpYV8i
bVDM9tZqUlejki9h9ZuS/sYIl0T4Aaa0QLYPMOvyl+zbLxfw0kmLI7VpFaUyxaWh
Oz/fGL5A+lI2BT2SLCdphmeTj5dQ4R9a2nqMYAmiOZmFAYJvMRzDmuooJ65KPPvx
xSsCbJhZoTp9JQz1nslWRcex7MCRth9BrL7wVu8hgb6RAw+lBkbpTeyQ7em5EjCb
h7xMmCjeBr7wouhnAz3p
=jYpU
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-08-21 17:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 16:43 [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess Paolo Bonzini
2013-08-21 16:43 ` [Qemu-devel] [PATCH 1/3] vl: allow "cont" from panicked state Paolo Bonzini
2013-08-21 16:43 ` [Qemu-devel] [PATCH 2/3] pc: get rid of builtin pvpanic Paolo Bonzini
2013-08-21 17:03   ` Michael S. Tsirkin
2013-08-21 17:02     ` Paolo Bonzini
2013-08-21 17:07       ` Andreas Färber
2013-08-21 17:04     ` Michael S. Tsirkin
2013-08-21 17:33   ` Michael S. Tsirkin
2013-08-21 16:43 ` [Qemu-devel] [PATCH 3/3] pvpanic: rename to isa-pvpanic Paolo Bonzini
2013-08-21 17:01   ` Michael S. Tsirkin
2013-08-21 17:01     ` Paolo Bonzini
2013-08-21 17:07       ` Michael S. Tsirkin
2013-08-21 17:06         ` Paolo Bonzini
2013-08-21 17:31           ` Michael S. Tsirkin
2013-08-22 12:43           ` Laszlo Ersek
2013-08-22 12:41             ` Paolo Bonzini
2013-08-25 10:44               ` Michael S. Tsirkin
2013-08-22 16:50             ` Anthony Liguori
2013-08-25 10:29               ` Michael S. Tsirkin
2013-08-21 17:35     ` Andreas Färber
2013-08-21 17:46       ` Paolo Bonzini
2013-08-21 16:48 ` [Qemu-devel] [RFC PATCH v2 0/3] Start fixing the pvpanic mess Daniel P. Berrange
2013-08-21 16:51   ` Paolo Bonzini
2013-08-21 16:55     ` Daniel P. Berrange
2013-08-21 16:56       ` Paolo Bonzini
2013-08-21 17:10         ` Eric Blake
2013-08-21 17:11           ` Paolo Bonzini [this message]
2013-08-22  9:17         ` Daniel P. Berrange
2013-08-21 17:02     ` Eric Blake
2013-08-21 17:10       ` Paolo Bonzini
2013-08-21 17:26       ` Michael S. Tsirkin
2013-08-21 17:30         ` Paolo Bonzini

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=5214F4CF.1080908@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lersek@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@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 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.