From: Eric Blake <eblake@redhat.com>
To: Aarushi Mehta <mehta.aaru20@gmail.com>, qemu-devel@nongnu.org
Cc: saket.sinha89@gmail.com, Julia Suvorova <jusual@mail.ru>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 1/9] qapi/block-core: add option for io_uring
Date: Tue, 21 May 2019 20:01:59 -0500 [thread overview]
Message-ID: <b3cffe45-ffac-b010-189d-b852e632c8d9@redhat.com> (raw)
In-Reply-To: <1c277edc76e47fbbaae0ecdd6774e24ac9a94ee5.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On 5/21/19 7:51 PM, Aarushi Mehta wrote:
>>> +# @io_uring: Use linux io_uring
>>
>> Missing a '(since 4.1)' tag.
>>
>>> #
>>> # Since: 2.9
>>> ##
>>> { 'enum': 'BlockdevAioOptions',
>>> - 'data': [ 'threads', 'native' ] }
>>> + 'data': [ 'threads', 'native','io_uring' ] }
>>
>> Missing space after ',' (not essential, but matching style is nice).
>> Should the new element be defined conditionally, so that
>> introspection
>> only sees the new enum member when compiled for Linux?
>>
> I'm not sure what would be the benefits of that? We already check for
> Linux at configure, and this would reduce readability. We aren't doing
> this for native.
Look at BlockdevOptionsFile in qapi/block-core.qapi. Telling the QAPI
generator that something is only available on Linux means that it will
be obvious to introspection (the QMP command query-qmp-schema) whether
the feature is present in a particular binary.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-22 1:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 23:52 [Qemu-devel] [RFC PATCH 0/9] Add support for io_uring Aarushi Mehta
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 1/9] qapi/block-core: add option " Aarushi Mehta
2019-05-22 0:39 ` Eric Blake
2019-05-22 0:51 ` Aarushi Mehta
2019-05-22 1:01 ` Eric Blake [this message]
2019-05-22 9:16 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-05-22 13:07 ` [Qemu-devel] " Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 2/9] block/block: add BDRV flag " Aarushi Mehta
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 3/9] include/block: declare interfaces " Aarushi Mehta
2019-05-22 13:09 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 4/9] stubs: add aio interface stubs " Aarushi Mehta
2019-05-22 13:10 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 5/9] util/asyn: add aio interfaces " Aarushi Mehta
2019-05-22 13:16 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 6/9] block/io_uring: implements " Aarushi Mehta
2019-05-22 15:43 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 7/9] blockdev: accept io_uring as option Aarushi Mehta
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 8/9] block/file-posix: extends to use with io_uring Aarushi Mehta
2019-05-22 15:45 ` Stefan Hajnoczi
2019-05-21 23:52 ` [Qemu-devel] [RFC PATCH 9/9] configure: permits use of io_uring with probe Aarushi Mehta
2019-05-22 0:09 ` [Qemu-devel] [RFC PATCH 0/9] Add support for io_uring no-reply
2019-05-22 15:46 ` Stefan Hajnoczi
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=b3cffe45-ffac-b010-189d-b852e632c8d9@redhat.com \
--to=eblake@redhat.com \
--cc=jusual@mail.ru \
--cc=mehta.aaru20@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=saket.sinha89@gmail.com \
--cc=stefanha@redhat.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).