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 v4] Add 'maxqdepth' as an option to tty character devices.
Date: Fri, 10 May 2013 21:28:14 -0600 [thread overview]
Message-ID: <518DBACE.5000904@redhat.com> (raw)
In-Reply-To: <1367966349-13242-1-git-send-email-john.baboval@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
On 05/07/2013 04:39 PM, 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.
>
> +++ 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
> -# @type: What kind of device this is.
> +#
> +# @maxqdepth: #optional The maximum depth of the underlying tty
> +# output queue (Unix) (Since 1.6)
> #
> # Since: 1.4
> ##
> -{ 'type': 'ChardevHostdev', 'data': { 'device' : 'str' } }
> +{ 'type': 'ChardevHostdev', 'data': { 'device' : 'str',
> + '*maxqdepth' : 'int' } }
>
Thanks; this interface change looks better (I'd still like to see
someone working on introspection, but it doesn't have to be you). I'll
still leave the implementation details to others more qualified for that
part of the review. In particular, since you are claiming this optional
attribute is Linux-only, that means we'd need introspection to know
whether a given qemu build supports the field (compiled on Linux) or not
(compiled on mingw), not just whether the qemu is new enough (1.6) or
older (1.4).
--
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-11 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 22:39 [Qemu-devel] [PATCH v4] Add 'maxqdepth' as an option to tty character devices John Baboval
2013-05-11 3:28 ` Eric Blake [this message]
2013-05-14 18:13 ` 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=518DBACE.5000904@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).