From: Peter Krempa <pkrempa@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, armbru@redhat.com, eblake@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] file-posix: Add dynamic-auto-read-only QAPI feature
Date: Mon, 8 Apr 2019 18:25:23 +0200 [thread overview]
Message-ID: <20190408162523.GG4288@angien.pipo.sk> (raw)
In-Reply-To: <20190408143543.3982-1-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Mon, Apr 08, 2019 at 16:35:39 +0200, Kevin Wolf wrote:
> This series adds optional feature lists to struct definitions in the
> QAPI schema and makes use of them to advertise the new behaviour of
> auto-read-only=on in file-posix.
>
> Kevin Wolf (4):
> qapi: Support features for structs
> tests/qapi-schema: Test for good feature lists in structs
> tests/qapi-schema: Error case tests for features in structs
> file-posix: Add dynamic-auto-read-only QAPI feature
I was able to implement this in libvirt fairly easy. My work-in-progress
(needs some docs and polishing) patches can be found at:
https://github.com/pipo/libvirt/commits/qapi-features-introspect
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Peter Krempa <pkrempa@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: armbru@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] file-posix: Add dynamic-auto-read-only QAPI feature
Date: Mon, 8 Apr 2019 18:25:23 +0200 [thread overview]
Message-ID: <20190408162523.GG4288@angien.pipo.sk> (raw)
Message-ID: <20190408162523.Nm7IfRkBaFR8zDu0RKqbawI7OIzYYeHfWhB07xM3zNU@z> (raw)
In-Reply-To: <20190408143543.3982-1-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Mon, Apr 08, 2019 at 16:35:39 +0200, Kevin Wolf wrote:
> This series adds optional feature lists to struct definitions in the
> QAPI schema and makes use of them to advertise the new behaviour of
> auto-read-only=on in file-posix.
>
> Kevin Wolf (4):
> qapi: Support features for structs
> tests/qapi-schema: Test for good feature lists in structs
> tests/qapi-schema: Error case tests for features in structs
> file-posix: Add dynamic-auto-read-only QAPI feature
I was able to implement this in libvirt fairly easy. My work-in-progress
(needs some docs and polishing) patches can be found at:
https://github.com/pipo/libvirt/commits/qapi-features-introspect
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-08 16:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 14:35 [Qemu-devel] [PATCH 0/4] file-posix: Add dynamic-auto-read-only QAPI feature Kevin Wolf
2019-04-08 14:35 ` Kevin Wolf
2019-04-08 14:35 ` [Qemu-devel] [PATCH 1/4] qapi: Support features for structs Kevin Wolf
2019-04-08 14:35 ` Kevin Wolf
2019-04-18 20:03 ` Markus Armbruster
2019-04-18 20:03 ` Markus Armbruster
2019-05-15 10:58 ` Kevin Wolf
2019-05-15 11:22 ` Peter Krempa
2019-05-15 13:48 ` Markus Armbruster
2019-05-17 13:43 ` Peter Krempa
2019-05-17 18:03 ` Markus Armbruster
2019-04-08 14:35 ` [Qemu-devel] [PATCH 2/4] tests/qapi-schema: Test for good feature lists in structs Kevin Wolf
2019-04-08 14:35 ` Kevin Wolf
2019-04-08 14:35 ` [Qemu-devel] [PATCH 3/4] tests/qapi-schema: Error case tests for features " Kevin Wolf
2019-04-08 14:35 ` Kevin Wolf
2019-04-08 14:35 ` [Qemu-devel] [PATCH 4/4] file-posix: Add dynamic-auto-read-only QAPI feature Kevin Wolf
2019-04-08 14:35 ` Kevin Wolf
2019-04-18 20:13 ` Markus Armbruster
2019-04-18 20:13 ` Markus Armbruster
2019-04-08 16:25 ` Peter Krempa [this message]
2019-04-08 16:25 ` [Qemu-devel] [PATCH 0/4] " Peter Krempa
2019-04-18 7:22 ` Kevin Wolf
2019-04-18 7:22 ` Kevin Wolf
2019-04-18 20:18 ` Markus Armbruster
2019-04-18 20:18 ` 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=20190408162523.GG4288@angien.pipo.sk \
--to=pkrempa@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).