qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, lilei@linux.vnet.ibm.com,
	qemu-devel@nongnu.org, lcapitulino@redhat.com, kraxel@redhat.com,
	akong@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] qemu-char: ringbuf fixes
Date: Fri, 26 Jul 2013 09:06:37 -0600	[thread overview]
Message-ID: <51F2907D.2030301@redhat.com> (raw)
In-Reply-To: <1374849874-25531-1-git-send-email-armbru@redhat.com>

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

On 07/26/2013 08:44 AM, Markus Armbruster wrote:
> Fix code to match documentation.  The patches take pains to preserve
> command-line, HMP and QMP bug-compatibility.  I'm not sure that's
> actually needed, because:
> 
> * All: the documented way to use the driver never worked in any
>   released version, and the way that worked was undocumented.
> 
> * QMP: I doubt anyone used chardev-add / chardev-remove in anger,
>   because serious use surely would've run into the bug fixed in commit
>   commit 2ea3e2c "qemu-char: Fix ID reuse after chardev-remove for
>   qapi-based init".
> 
> I include the compatibility gunk anyway, so we can have a more
> informed discussion.

Libvirt 1.1.1 has added patches that try to use chardev-add; but so far,
it only uses 'null', 'pty', 'file', 'parallel', 'serial', and 'socket'
backends.  But if libvirt adds support for a ringbuf device, it would be
nice to support it on as many qemu versions at once as possible, rather
than having to determine whether qemu is new enough to have fixed
semantics vs. using the undocumented backend of the older semantics.  So
I appreciate the attempt at back-compat.

> 
> You might want to apply this after my "Our QAPI parser is a hack,																																																	
> replace it" series, so the indented comment in PATCH 3/3 works by
> design rather than accident.

Heh :)

Series:
Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
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: 621 bytes --]

  parent reply	other threads:[~2013-07-26 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 14:44 [Qemu-devel] [PATCH v2 0/3] qemu-char: ringbuf fixes Markus Armbruster
2013-07-26 14:44 ` [Qemu-devel] [PATCH v2 1/3] Revert "chardev: Make the name of memory device consistent" Markus Armbruster
2013-07-26 14:44 ` [Qemu-devel] [PATCH v2 2/3] qemu-char: Register ring buffer driver with correct name "ringbuf" Markus Armbruster
2013-07-26 14:44 ` [Qemu-devel] [PATCH v2 3/3] qapi: Rename ChardevBackend member "memory" to "ringbuf" Markus Armbruster
2013-07-26 15:06 ` Eric Blake [this message]
2013-07-29 20:24 ` [Qemu-devel] [PATCH v2 0/3] qemu-char: ringbuf fixes Anthony Liguori

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=51F2907D.2030301@redhat.com \
    --to=eblake@redhat.com \
    --cc=akong@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lilei@linux.vnet.ibm.com \
    --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).