All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Mark Wu <wudxw@linux.vnet.ibm.com>,
	Qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Extend qemu-ga's 'guest-info' command to expose flag 'success-response'
Date: Tue, 24 Sep 2013 13:13:08 -0600	[thread overview]
Message-ID: <5241E444.4040606@redhat.com> (raw)
In-Reply-To: <20130924190032.7651.74662@loki>

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

On 09/24/2013 01:00 PM, Michael Roth wrote:
> Quoting Mark Wu (2013-09-22 01:50:54)
>> Now we have several qemu-ga commands not returning response on success.
>> It has been documented in qga/qapi-schema.json already. This patch exposes
>> the 'success-response' flag by extending 'guest-info' command. With this
>> change, the clients can handle the command response more flexibly.
>>
>> Changes:
>>         v2: add the notation 'since 1.7' to the option 'success-response'
>>         (per Eric Blake's comments)
>>
>> Signed-off-by: Mark Wu <wudxw@linux.vnet.ibm.com>
> 
> Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> 
> Eric, do we have your reviewed-by other than the changes you mentioned? If so I
> can fix those up in my tree.

Aha - force me to do a FULL review, rather than just an interface
review.  I found more issues, so this probably deserves a v2:

>> +bool qmp_command_has_success_response(const char *name)
>> +{
>> +    QmpCommand *cmd;
>> +
>> +    QTAILQ_FOREACH(cmd, &qmp_commands, node) {
>> +        if (strcmp(cmd->name, name) == 0) {
>> +            return cmd->options != QCO_NO_SUCCESS_RESP;

cmd->options is a bitmask - it is feasible that we may add more QCO_NO_*
flags in the future, at which point inequality is NOT correct.  Rather,
you want:

return !(cmd->options & QCO_NO_SUCCESS_RESP);

>> +++ b/qga/commands.c
>> @@ -63,6 +63,8 @@ struct GuestAgentInfo *qmp_guest_info(Error **err)
>>          cmd_info = g_malloc0(sizeof(GuestAgentCommandInfo));
>>          cmd_info->name = g_strdup(*cmd_list);
>>          cmd_info->enabled = qmp_command_is_enabled(cmd_info->name);
>> +        cmd_info->success_response =
>> +            qmp_command_has_success_response(cmd_info->name);

This feels wasteful.  Why are we doing an O(n) lookup for BOTH
qmp_command_is_enabled AND qmp_command_has_success_response, in an O(n)
loop over command names?  That's O(n^2) in the number of commands.
Better would be getting a list of QmpCommand* instead of a list of
char*, and looking directly in each object, for O(n) computation of the
results.

-- 
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: 621 bytes --]

  reply	other threads:[~2013-09-24 19:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22  6:50 [Qemu-devel] [PATCH] Extend qemu-ga's 'guest-info' command to expose flag 'success-response' Mark Wu
2013-09-23 12:32 ` Luiz Capitulino
2013-09-23 13:57 ` Eric Blake
2013-09-24 19:00 ` Michael Roth
2013-09-24 19:13   ` Eric Blake [this message]
2013-09-24 21:07     ` Michael Roth
2013-09-25  0:34       ` Luiz Capitulino
2013-09-25 12:30         ` Mark Wu
  -- strict thread matches above, loose matches on Subject: below --
2013-09-18  7:23 Mark Wu
2013-09-18 12:45 ` Luiz Capitulino
2013-09-18 12:59 ` Eric Blake

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=5241E444.4040606@redhat.com \
    --to=eblake@redhat.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=wudxw@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.