qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/7] file-posix: Add dynamic-auto-read-only QAPI feature
Date: Thu, 6 Jun 2019 10:54:16 -0500	[thread overview]
Message-ID: <2d2f4567-1b35-6586-e195-a89b398e676c@redhat.com> (raw)
In-Reply-To: <20190606153803.5278-7-armbru@redhat.com>

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

On 6/6/19 10:38 AM, Markus Armbruster wrote:
> From: Kevin Wolf <kwolf@redhat.com>
> 
> In commit 23dece19da4 ('file-posix: Make auto-read-only dynamic') ,
> auto-read-only=on changed its behaviour in file-posix for the 4.0
> release. This change cannot be detected through the usual mechanisms
> like schema introspection. Add a new feature flag to the schema to
> allow libvirt to detect the presence of the new behaviour.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  qapi/block-core.json | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 1defcde048..f5e1ee91f9 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2859,6 +2859,15 @@
>  #                         file is large, do not use in production.
>  #                         (default: off) (since: 3.0)
>  #
> +# Features:
> +# @dynamic-auto-read-only: If present, enabled auto-read-only means that the
> +#                          driver will open the image read-only at first,
> +#                          dynamically reopen the image file read-write when
> +#                          the first writer is attached to the node and reopen
> +#                          read-only when the last writer is detached. This
> +#                          allows to give QEMU write permissions only on demand

s/allows to give/allows giving/

> +#                          when an operation actually needs write access.
> +#
>  # Since: 2.9
>  ##
>  { 'struct': 'BlockdevOptionsFile',
> @@ -2868,7 +2877,9 @@
>              '*aio': 'BlockdevAioOptions',
>  	    '*drop-cache': {'type': 'bool',
>  	                    'if': 'defined(CONFIG_LINUX)'},
> -            '*x-check-cache-dropped': 'bool' } }
> +            '*x-check-cache-dropped': 'bool' },
> +  'features': [ { 'name': 'dynamic-auto-read-only',
> +                  'if': 'defined(CONFIG_POSIX)' } ] }
>  
>  ##
>  # @BlockdevOptionsNull:
> 

-- 
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 --]

  reply	other threads:[~2019-06-06 15:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 15:37 [Qemu-devel] [PATCH 0/7] file-posix: Add dynamic-auto-read-only QAPI feature Markus Armbruster
2019-06-06 15:37 ` [Qemu-devel] [PATCH 1/7] qapi: Add feature flags to struct types Markus Armbruster
2019-06-06 15:37 ` [Qemu-devel] [PATCH 2/7] tests/qapi-schema: Test for good feature lists in structs Markus Armbruster
2019-06-06 15:37 ` [Qemu-devel] [PATCH 3/7] tests/qapi-schema: Error case tests for features " Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 4/7] qapi: Disentangle QAPIDoc code Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 5/7] qapi: Allow documentation for features Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 6/7] file-posix: Add dynamic-auto-read-only QAPI feature Markus Armbruster
2019-06-06 15:54   ` Eric Blake [this message]
2019-06-12 16:31     ` Markus Armbruster
2019-06-06 15:38 ` [Qemu-devel] [PATCH 7/7] qapi: Simplify QAPIDoc implements its state machine Markus Armbruster
2019-06-07 15:02 ` [Qemu-devel] [PATCH 0/7] file-posix: Add dynamic-auto-read-only QAPI feature Kevin Wolf
2019-06-12 16:45 ` Markus Armbruster

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=2d2f4567-1b35-6586-e195-a89b398e676c@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).