qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>, Mark Wu <wudxw@linux.vnet.ibm.com>
Cc: Qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add interface to traverse the qmp command list by QmpCommand
Date: Fri, 27 Sep 2013 11:07:26 -0500	[thread overview]
Message-ID: <20130927160726.20300.75624@loki> (raw)
In-Reply-To: <5243A2A3.2000502@redhat.com>

Quoting Eric Blake (2013-09-25 21:57:39)
> On 09/25/2013 07:56 PM, Mark Wu wrote:
> > In the original code, qmp_get_command_list is used to construct
> > a list of all commands' name. To get the information of all qga
> > commands, it traverses the name list and search the command info
> > with its name.  So it can cause O(n^2) in the number of commands.
> > 
> > This patch adds an interface to traverse the qmp command list by
> > QmpCommand to replace qmp_get_command_list. It can decrease the
> > complexity from O(n) to O(n^2)
> 
> from O(n^2) to O(n)
> 
> > 
> > Signed-off-by: Mark Wu <wudxw@linux.vnet.ibm.com>
> > ---
> >  include/qapi/qmp/dispatch.h |  3 +-
> >  qapi/qmp-registry.c         | 28 ++-----------------
> >  qga/commands.c              | 39 ++++++++++----------------
> >  qga/main.c                  | 68 +++++++++++++++++----------------------------
> >  4 files changed, 45 insertions(+), 93 deletions(-)
> > 
> 
> >  
> > -bool qmp_command_is_enabled(const char *name)
> 
> I think one of Michael's suggestions was that you may still want
> qmp_command_is_enabled, but with a new signature:
> 
> bool qmp_command_is_enabled(const QmpCommand *cmd)
> {
>     return cmd->enabled;
> }

That would still be my preference, as I can see the underlying
fields changing somewhat in a future where QMP starts using the same
infrastructure, and new users come along like qemu-ga guest->host
commands we did as part of GSoC.

Wouldn't hold things up in the meantime, but if we're re-spinning
anyway let's maintain the precedence of using getter/setter funcs
for QmpCommand.

> 
> > -struct GuestAgentInfo *qmp_guest_info(Error **err)
> > +static void qmp_command_info(QmpCommand *cmd, void *opaque)
> >   {
> > -    GuestAgentInfo *info = g_malloc0(sizeof(GuestAgentInfo));
> > +    GuestAgentInfo *info = (GuestAgentInfo *)opaque; 
> 
> 
> > -        cmd_info->enabled = qmp_command_is_enabled(cmd_info->name);
> >  
> > -        cmd_info_list = g_malloc0(sizeof(GuestAgentCommandInfoList));
> > -        cmd_info_list->value = cmd_info;
> > -        cmd_info_list->next = info->supported_commands;
> > -        info->supported_commands = cmd_info_list;
> > +    cmd_info = g_malloc0(sizeof(GuestAgentCommandInfo));
> > +    cmd_info->name = g_strdup(cmd->name);
> > +    cmd_info->enabled = cmd->enabled;
> 
> I guess it all depends on whether we want QmpCommand to be an opaque
> type outside of a single file.  But I don't have a strong argument for
> making it opaque, and your approach works if we don't mind exposing the
> details of QmpCommand across multiple files.  So I can live with your
> patch as-is.
> 
> 
> > +static void ga_enable_non_blacklisted(QmpCommand *cmd, void *opaque)
> >  {
> 
> > +    GList *blacklist = (GList *)opaque;
> 
> Again, the cast is not necessary.
> 
> Overall, I like the patch.  Just a few tweaks suggested, but I can live
> with you adding:
> 
> Reviewed-by: Eric Blake <eblake@redhat.com>
> 
> -- 
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org

  reply	other threads:[~2013-09-27 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26  1:56 [Qemu-devel] [PATCH] Add interface to traverse the qmp command list by QmpCommand Mark Wu
2013-09-26  2:36 ` Mark Wu
2013-09-26  2:57 ` Eric Blake
2013-09-27 16:07   ` Michael Roth [this message]
2013-09-27 16:16 ` Michael Roth

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=20130927160726.20300.75624@loki \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=eblake@redhat.com \
    --cc=lcapitulino@redhat.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 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).