From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH for-6.0] qapi: qom: do not use target-specific conditionals
Date: Fri, 26 Mar 2021 12:49:35 +0100 [thread overview]
Message-ID: <87a68ae5-74fc-cb36-f78e-d40128a23e3c@redhat.com> (raw)
In-Reply-To: <87r1k2tc70.fsf@dusky.pond.sub.org>
On 26/03/21 11:57, Markus Armbruster wrote:
>> 'rng-random': 'RngRandomProperties',
>> 'secret': 'SecretProperties',
>> 'secret_keyring': 'SecretKeyringProperties',
>> - 'sev-guest': { 'type': 'SevGuestProperties',
>> - 'if': 'defined(CONFIG_SEV)' },
>> + 'sev-guest': 'SevGuestProperties',
>> 'throttle-group': 'ThrottleGroupProperties',
>> 'tls-creds-anon': 'TlsCredsAnonProperties',
>> 'tls-creds-psk': 'TlsCredsPskProperties',
>
> No branch for tag value 'pef-guest', i.e. no tag-specific members.
> There are two more: can_bus, s390_pv_guest. I assume this is
> intentional.
Yes, they have no properties.
> Links a bit of dead code into the other qemu-system-FOO, but that's
> okay.
>
> If we genuinely needed (or wanted) target-dependent -object, we'd split
> qom-target.json off qom.json, and put the target-dependent parts there,
> including the enum and the union, with the obvious ripple effects. Not
> now, maybe not ever.
>
> Would adding "only for CONFIG_MUMBLE" to the doc comments make sense?
> It's what we did before we had 'if'.
In this specific case we had not documentation at all for objects. We
can add the information on relevant targets in the documentation for the
*Properties types.
Paolo
next prev parent reply other threads:[~2021-03-26 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 10:03 [PATCH for-6.0] qapi: qom: do not use target-specific conditionals Paolo Bonzini
2021-03-26 10:57 ` Markus Armbruster
2021-03-26 11:49 ` Paolo Bonzini [this message]
2021-03-26 12:27 ` Markus Armbruster
2021-03-26 14:50 ` Paolo Bonzini
2021-03-26 13:45 ` Tom Lendacky
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=87a68ae5-74fc-cb36-f78e-d40128a23e3c@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.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).