qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: arei.gonglei@huawei.com, qemu-devel@nongnu.org
Cc: weidong.huang@huawei.com, aliguori@amazon.com, mst@redhat.com,
	armbru@redhat.com, luonengjun@huawei.com,
	peter.huangpeng@huawei.com, lcapitulino@redhat.com,
	stefanha@redhat.com, pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 6/7] qmp: print descriptions of object properties
Date: Mon, 29 Sep 2014 10:27:19 -0600	[thread overview]
Message-ID: <54298867.3040604@redhat.com> (raw)
In-Reply-To: <1411794841-9672-7-git-send-email-arei.gonglei@huawei.com>

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

On 09/26/2014 11:14 PM, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
> 
> Add a new "description" field to DevicePropertyInfo.
> The descriptions can serve as documentation in the code,
> and they can be used to provide better help. For example:
> 
> $./qemu-system-x86_64 -device virtio-blk-pci,?
> 

> +++ b/qapi-schema.json
> @@ -1615,11 +1615,12 @@
>  #
>  # @name: the name of the property
>  # @type: the typename of the property
> +# @description: the description of the property

Please add a '(since 2.2)' designation.  Will 'description' always be
present (that is, do ALL properties have a description), or is it
optional and only provided when a non-NULL description is available?

[/me reads rest of patch]

Yes, given your code, it looks like you meant for it to be optional.

>  #
>  # Since: 1.2
>  ##
>  { 'type': 'DevicePropertyInfo',
> -  'data': { 'name': 'str', 'type': 'str' } }
> +  'data': { 'name': 'str', 'type': 'str', 'description': 'str' } }

Therefore, this needs to be '*description'...

>  
>  ##
>  # @device-list-properties:
> diff --git a/qdev-monitor.c b/qdev-monitor.c
> index 5ec6606..5ee6bf2 100644
> --- a/qdev-monitor.c
> +++ b/qdev-monitor.c
> @@ -213,9 +213,14 @@ int qdev_device_help(QemuOpts *opts)
>      }
>  
>      for (prop = prop_list; prop; prop = prop->next) {
> -        error_printf("%s.%s=%s\n", driver,
> +        error_printf("%s.%s=%s", driver,
>                       prop->value->name,
>                       prop->value->type);
> +        if (prop->value->description) {

...and this needs to be 'prop->value->has_description'.  We don't
support NULL values of non-optional strings in QMP yet.

> @@ -465,7 +466,9 @@ static DevicePropertyInfo *make_device_property_info(ObjectClass *klass,
>  
>              info = g_malloc0(sizeof(*info));
>              info->name = g_strdup(prop->name);
> -            info->type = g_strdup(prop->info->legacy_name ?: prop->info->name);
> +            info->type = g_strdup(prop->info->name);
> +            info->description = prop->info->description ?
> +                                g_strdup(prop->info->description) : NULL;

This needs to be:

info->has_description = !!prop->info->description;
info->description = g_strdup(prop->info->description);

(it's safe to call g_strdup(NULL), avoiding the need for ?: in the
assignment).

>              return info;
>          }
>          klass = object_class_get_parent(klass);
> @@ -475,6 +478,8 @@ static DevicePropertyInfo *make_device_property_info(ObjectClass *klass,
>      info = g_malloc0(sizeof(*info));
>      info->name = g_strdup(name);
>      info->type = g_strdup(default_type);
> +    info->description = description ? g_strdup(description) : NULL;

Another place that should avoid the ?:, and set has_description.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]

  reply	other threads:[~2014-09-29 16:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27  5:13 [Qemu-devel] [PATCH v3 0/7] add description field in ObjectProperty and PropertyInfo struct arei.gonglei
2014-09-27  5:13 ` [Qemu-devel] [PATCH v3 1/7] qom: add error handler for object_property_print() arei.gonglei
2014-09-27  5:13 ` [Qemu-devel] [PATCH v3 2/7] qom: add error handler for object alias property arei.gonglei
2014-09-27  5:13 ` [Qemu-devel] [PATCH v3 3/7] qdev: add description field in PropertyInfo struct arei.gonglei
2014-09-27  5:13 ` [Qemu-devel] [PATCH v3 4/7] qom: add description field in ObjectProperty struct arei.gonglei
2014-09-29 13:35   ` Paolo Bonzini
2014-09-30  1:45     ` Gonglei (Arei)
2014-09-27  5:13 ` [Qemu-devel] [PATCH v3 5/7] qdev: set the object property's description to the qdev property's arei.gonglei
2014-09-27  5:14 ` [Qemu-devel] [PATCH v3 6/7] qmp: print descriptions of object properties arei.gonglei
2014-09-29 16:27   ` Eric Blake [this message]
2014-09-30  1:49     ` Gonglei (Arei)
2014-09-27  5:14 ` [Qemu-devel] [PATCH v3 7/7] qdev: drop legacy_name from qdev properties arei.gonglei
2014-09-29 15:15 ` [Qemu-devel] [PATCH v3 0/7] add description field in ObjectProperty and PropertyInfo struct Andreas Färber
2014-09-30  0:58   ` Gonglei (Arei)

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=54298867.3040604@redhat.com \
    --to=eblake@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.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).