qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Roman Kagan <rkagan@virtuozzo.com>,
	"Denis V. Lunev" <den@openvz.org>,
	Igor Redko <redkoi@virtuozzo.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] virtio-balloon: export all balloon statistics
Date: Wed, 24 Feb 2016 08:43:35 -0700	[thread overview]
Message-ID: <56CDCFA7.90308@redhat.com> (raw)
In-Reply-To: <20160224162344-mutt-send-email-mst@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

On 02/24/2016 07:31 AM, Michael S. Tsirkin wrote:
>> One of the benefits is forward compatibility, so that counters that have
>> graduated into supported ones and have got their own number and name,
>> can be made to work with qemu that doesn't yet recognize them.
> 
> Then management does start relying on the x- prefixed things,
> and once it's used to that it's a slippery slope.

Any management tool that relies on an x- prefix name is broken.  We've
explicitly documented that the x- prefix is unstable and liable to go
away with a future release. Any management app that wants to use a
feature beginning with x- should FIRST push hard to get the x- removed
and stabilize the interface (and libvirt, at least, does just that).

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-02-24 15:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 14:59 [Qemu-devel] [PATCH v2 0/2] virtio-balloon: improve balloon statistics Denis V. Lunev
2016-02-23 14:59 ` [Qemu-devel] [PATCH 1/2] virtio-balloon: export all " Denis V. Lunev
2016-02-23 15:24   ` Michael S. Tsirkin
2016-02-23 15:29     ` Denis V. Lunev
2016-02-23 15:49       ` Michael S. Tsirkin
2016-02-24 10:01         ` Roman Kagan
2016-02-24 14:31           ` Michael S. Tsirkin
2016-02-24 15:43             ` Eric Blake [this message]
2016-02-25  5:50               ` Denis V. Lunev
2016-02-25  8:44                 ` Markus Armbruster
2016-02-25  8:54                   ` Michael S. Tsirkin
2016-02-25  9:30                     ` Roman Kagan
2016-02-25 10:05                       ` Michael S. Tsirkin
2016-02-25 10:46                         ` Markus Armbruster
2016-02-25 11:17                           ` Roman Kagan
2016-02-25 11:58                             ` Markus Armbruster
2016-02-25 12:44                               ` Roman Kagan
2016-02-25 14:10                                 ` Markus Armbruster
2016-02-25 14:49                                   ` Roman Kagan
2016-02-23 14:59 ` [Qemu-devel] [PATCH 2/2] virtio-balloon: add 'available' counter Denis V. Lunev
  -- strict thread matches above, loose matches on Subject: below --
2016-02-24  7:50 [Qemu-devel] [PATCH v3 0/2] virtio-balloon: improve balloon statistics Denis V. Lunev
2016-02-24  7:50 ` [Qemu-devel] [PATCH 1/2] virtio-balloon: export all " Denis V. Lunev
2016-02-20  7:54 [Qemu-devel] [PATCH 0/2] virtio-balloon: improve " Denis V. Lunev
2016-02-20  7:54 ` [Qemu-devel] [PATCH 1/2] virtio-balloon: export all " Denis V. Lunev
2016-02-22 21:27   ` Eric Blake

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=56CDCFA7.90308@redhat.com \
    --to=eblake@redhat.com \
    --cc=den@openvz.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=redkoi@virtuozzo.com \
    --cc=rkagan@virtuozzo.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).