From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v3 4/4] migration/qapi: Drop @MigrationParameter enum
Date: Mon, 16 Oct 2023 19:36:09 +0200 [thread overview]
Message-ID: <87v8b6eagm.fsf@pond.sub.org> (raw)
In-Reply-To: <ZS1h+pNhqyaXHDhW@x1n> (Peter Xu's message of "Mon, 16 Oct 2023 12:16:58 -0400")
Peter Xu <peterx@redhat.com> writes:
> On Mon, Oct 16, 2023 at 08:29:58AM +0200, Markus Armbruster wrote:
>> Better, because even stupider: drop the feature flags. They have no
>> effect on internal use, and there is no external use.
>>
>> ##
>> # @MigrationParameter:
>> #
>> # TODO: elide from generated documentation (type is used only
>> # internally, and not visible in QMP)
>> #
>> # Since: 2.4
>> ##
>> { 'enum': 'MigrationParameter',
>> 'data': ['announce-initial', 'announce-max',
>> 'announce-rounds', 'announce-step',
>> 'compress-level', 'compress-threads', 'decompress-threads',
>> 'compress-wait-thread', 'throttle-trigger-threshold',
>> 'cpu-throttle-initial', 'cpu-throttle-increment',
>> 'cpu-throttle-tailslow',
>> 'tls-creds', 'tls-hostname', 'tls-authz', 'max-bandwidth',
>> 'downtime-limit',
>> 'x-checkpoint-delay',
>> 'block-incremental',
>> 'multifd-channels',
>> 'xbzrle-cache-size', 'max-postcopy-bandwidth',
>> 'max-cpu-throttle', 'multifd-compression',
>> 'multifd-zlib-level', 'multifd-zstd-level',
>> 'block-bitmap-mapping',
>> 'x-vcpu-dirty-limit-period',
>> 'vcpu-dirty-limit'] }
>
> Didn't work either, unfortunately.. Compile is fine, but I still see the
> lines generated in qemu-qmp-ref.7.
>
> MigrationParameter (Enum)
> Values
> announce-initial
> Not documented
>
> announce-max
> Not documented
>
> announce-rounds
> Not documented
>
> announce-step
> Not documented
>
> compress-level
> Not documented
> [...]
I didn't claim these will *not* be generated :)
> Patch attached.
>
> Thanks,
Solutions:
0. Do nothing
The QEMU QMP Reference manual documents MigrationParameter, even
though it is not actually visible in QMP.
The documentation source is a duplicate.
1. Dumb down MigrationParameter's doc comment (your attached patch)
The QEMU QMP Reference manual documents MigrationParameter, even
though it is not actually visible in QMP. In addition to useless,
the documentation is embarrassing: lots of "Not documented".
2. Make MigrationParameter a C enum instead of a QAPI enum (your v3
patch)
The QEMU QMP Reference manual doesn't uselessly document
MigrationParameter (it still uselessly documents other internal-only
things).
We replace 20 lines of QAPI schema by 100 lines of C.
3. Improve the QAPI generator to generate docs only for definitions
visible externally, and to require doc comments only then
The QEMU QMP Reference manual doesn't uselessly document
internal-only stuff.
This solution doesn't exist, yet.
next prev parent reply other threads:[~2023-10-16 17:36 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 16:23 [PATCH v3 0/4] qapi/migration: Dedup migration parameter objects and fix tls-authz crash Peter Xu
2023-09-05 16:23 ` [PATCH v3 1/4] migration/qmp: Fix crash on setting tls-authz with null Peter Xu
2023-09-28 4:47 ` Michael Tokarev
2023-09-28 5:36 ` Markus Armbruster
2023-09-28 6:56 ` Michael Tokarev
2023-10-04 13:58 ` Juan Quintela
2023-10-16 6:05 ` Markus Armbruster
2023-09-05 16:23 ` [PATCH v3 2/4] tests/migration-test: Add a test for null parameter setups Peter Xu
2023-10-04 13:58 ` Juan Quintela
2023-09-05 16:23 ` [PATCH v3 3/4] migration/qapi: Replace @MigrateSetParameters with @MigrationParameters Peter Xu
2023-09-26 20:40 ` Markus Armbruster
2023-10-02 19:52 ` Peter Xu
2023-10-09 12:25 ` Markus Armbruster
2023-10-10 15:05 ` Peter Xu
2023-10-10 19:18 ` Markus Armbruster
2023-10-10 20:09 ` Peter Xu
2023-10-11 4:28 ` Markus Armbruster
2023-10-11 14:21 ` Markus Armbruster
2023-10-12 19:28 ` Peter Xu
2023-10-13 5:36 ` Markus Armbruster
2023-10-31 11:08 ` Juan Quintela
2023-11-02 14:25 ` Configuring migration (was: [PATCH v3 3/4] migration/qapi: Replace @MigrateSetParameters with @MigrationParameters) Markus Armbruster
2023-11-02 18:05 ` Peter Xu
2023-11-14 7:27 ` Configuring migration Markus Armbruster
2023-11-14 10:20 ` Juan Quintela
2023-11-14 9:13 ` Configuring migration (was: [PATCH v3 3/4] migration/qapi: Replace @MigrateSetParameters with @MigrationParameters) Daniel P. Berrangé
2023-11-14 9:53 ` Configuring migration Markus Armbruster
2023-11-14 9:55 ` Daniel P. Berrangé
2023-11-14 10:28 ` Juan Quintela
2023-11-14 10:34 ` Daniel P. Berrangé
2023-11-14 10:42 ` Juan Quintela
2023-11-14 10:45 ` Daniel P. Berrangé
2023-10-12 15:58 ` [PATCH v3 3/4] migration/qapi: Replace @MigrateSetParameters with @MigrationParameters Peter Xu
2023-10-13 5:41 ` Markus Armbruster
2023-09-05 16:23 ` [PATCH v3 4/4] migration/qapi: Drop @MigrationParameter enum Peter Xu
2023-09-06 4:42 ` Philippe Mathieu-Daudé
2023-09-06 9:00 ` Daniel P. Berrangé
2023-09-06 10:14 ` Philippe Mathieu-Daudé
2023-09-06 10:46 ` Daniel P. Berrangé
2023-09-26 19:05 ` Peter Xu
2023-09-26 20:43 ` Markus Armbruster
2023-10-02 20:42 ` Peter Xu
2023-10-16 6:29 ` Markus Armbruster
2023-10-16 16:16 ` Peter Xu
2023-10-16 17:36 ` Markus Armbruster [this message]
2023-09-25 12:59 ` [PATCH v3 0/4] qapi/migration: Dedup migration parameter objects and fix tls-authz crash Markus Armbruster
2023-09-26 17:06 ` Peter Xu
2023-09-26 20:03 ` Markus Armbruster
2023-10-16 7:08 ` Markus Armbruster
2023-10-16 16:29 ` Peter Xu
2023-10-17 6:32 ` Markus Armbruster
2023-10-17 15:28 ` Peter Xu
2023-10-18 5:38 ` Markus Armbruster
2023-10-25 13:17 ` QAPI doc generator improvements (was: [PATCH v3 0/4] qapi/migration: Dedup migration parameter objects and fix tls-authz crash) 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=87v8b6eagm.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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).