All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Eric Blake <eblake@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Roman Kagan <rkagan@virtuozzo.com>,
	Igor Redko <redkoi@virtuozzo.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] virtio-balloon: export all balloon statistics
Date: Thu, 25 Feb 2016 08:50:35 +0300	[thread overview]
Message-ID: <56CE962B.40809@openvz.org> (raw)
In-Reply-To: <56CDCFA7.90308@redhat.com>

On 02/24/2016 06:43 PM, Eric Blake wrote:
> 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).
>
this was exactly an original idea. Names started with 'x-' are
_officially_ unstable and for debug purpose. That is why I'd
prefer if v2 of the patchset will be taken.

Thank you.

  reply	other threads:[~2016-02-25  5:50 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
2016-02-25  5:50               ` Denis V. Lunev [this message]
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=56CE962B.40809@openvz.org \
    --to=den@openvz.org \
    --cc=eblake@redhat.com \
    --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 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.