qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: pkrempa@redhat.com, marcel.a@redhat.com, libvir-list@redhat.com,
	hutao@cn.fujitsu.com, "Michael S. Tsirkin" <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
Subject: Re: [Qemu-devel] [PATCH 3/3] pvpanic: rename to isa-pvpanic
Date: Wed, 21 Aug 2013 19:46:19 +0200	[thread overview]
Message-ID: <5214FCEB.5090805@redhat.com> (raw)
In-Reply-To: <5214FA56.3030509@suse.de>

Il 21/08/2013 19:35, Andreas Färber ha scritto:
> Am 21.08.2013 19:01, schrieb Michael S. Tsirkin:
>> On Wed, Aug 21, 2013 at 06:43:16PM +0200, Paolo Bonzini wrote:
>>> The pvpanic situation is already messed up enough.  Let us give our
>>> libvirt friends an easy indication that we have untied our side.
>>>
>>> Not-yet-signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>> ... because we first have to determine how to expose the device's existence
>>>     in the ACPI tables or in fw_cfg.
>>>
>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> So it's isa-pvpanic meaning "I-am-sure-this-is-the-last-bug-pvpanic"
>>
>> If we feel there's need to give libvirt a way to do
>> introspection into QEMU bugs, let's architect one.
>> Randomly renaming devices in the vain hope it's
>> the last major bug is not it.
>>
>> NACK
> 
> Seconded. While we shouldn't rule out renaming devices, doing so as a
> criteria for libvirt sounds utterly wrong.
> 
> Paolo, you are right that a single "NACK" cannot be a criteria, but a
> single convincing justification by a random reviewer should be
> sufficient to reconsider. :)
> 
> Adding some device property or obtaining the info via some existing
> query-* QMP command might be better alternatives.

Device properties are a good way to communicate changes to the guest,
but here the guest ABI is unchanged.

Anyhow, this patch is not strictly necessary.  It's just a safety net to
avoid that libvirt uses a buggy device on buggy versions of QEMU.

Paolo

  reply	other threads:[~2013-08-21 17:47 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 [this message]
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
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=5214FCEB.5090805@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@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 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).