From: Eric Blake <eblake@redhat.com>
To: John Baboval <john.baboval@citrix.com>
Cc: "John V. Baboval" <john.baboval@virtualcomputer.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add 'maxqdepth' as an option to tty character devices.
Date: Mon, 06 May 2013 08:43:25 -0600 [thread overview]
Message-ID: <5187C18D.5030901@redhat.com> (raw)
In-Reply-To: <1367847791-9214-1-git-send-email-john.baboval@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
On 05/06/2013 07:43 AM, John Baboval wrote:
> From: "John V. Baboval" <john.baboval@virtualcomputer.com>
>
> This parameter will cause writes to tty backed chardevs to return
> -EAGAIN if the backing tty has buffered more than the specified
> number of characters. When data is sent, the TIOCOUTQ ioctl is invoked
> to determine the current TTY output buffer depth.
>
Reviewing just the interface portion of the patch:
> +++ b/qapi-schema.json
> @@ -3182,11 +3182,14 @@
> #
> # @device: The name of the special file for the device,
> # i.e. /dev/ttyS0 on Unix or COM1: on Windows
> +# @maxqdepth: The maximum depth of the underlying tty
> + output queue (Unix)
Trailing whitespace. Run your patch through scripts/checkpatch.pl.
Since you are adding a new member, you should use a "(since 1.6)"
comment on this line. Also, most interfaces tend to use a blank line
between member documentation.
> # @type: What kind of device this is.
Hmm - we have a pre-existing documentation bug - this line probably
should have been deleted during commit d36b2b90.
> #
> # Since: 1.4
> ##
> -{ 'type': 'ChardevHostdev', 'data': { 'device' : 'str' } }
> +{ 'type': 'ChardevHostdev', 'data': { 'device' : 'str',
> + 'maxqdepth' : 'int' } }
Ouch - this says that maxqdepth is mandatory. But that is a
backwards-incompatible change with apps that target the 'chardev-add'
QMP command of qemu 1.4. You MUST make it optional, since older apps
will not be providing it.
--
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 --]
next prev parent reply other threads:[~2013-05-06 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 13:43 [Qemu-devel] [PATCH] Add 'maxqdepth' as an option to tty character devices John Baboval
2013-05-06 13:47 ` Paolo Bonzini
2013-05-07 16:36 ` [Qemu-devel] (no subject) John Baboval
2013-05-07 16:36 ` [Qemu-devel] [PATCH] Add 'maxqdepth' as an option to tty character devices John Baboval
2013-05-07 16:40 ` John Baboval
2013-05-06 14:43 ` Eric Blake [this message]
2013-05-07 16:51 ` [Qemu-devel] [PATCH v3] " John Baboval
2013-05-07 16:51 ` [Qemu-devel] [PATCH] " John Baboval
2013-05-07 17:17 ` Eric Blake
2013-05-07 22:24 ` John Baboval
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=5187C18D.5030901@redhat.com \
--to=eblake@redhat.com \
--cc=john.baboval@citrix.com \
--cc=john.baboval@virtualcomputer.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).