qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] let qemu-img info genereate json output
Date: Mon, 30 Jul 2012 15:34:11 +0100	[thread overview]
Message-ID: <20120730143411.GB10211@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1343384448-21828-1-git-send-email-xiawenc@linux.vnet.ibm.com>

On Fri, Jul 27, 2012 at 06:20:48PM +0800, Wenchao Xia wrote:
>   This patch would add option -j in qemu-img info command, which
> would generate json output in stdout.
> 
> Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
> ---
>  qemu-img.c |  306 +++++++++++++++++++++++++++++++++++++++++++++++++++--------
>  1 files changed, 264 insertions(+), 42 deletions(-)
> 
> diff --git a/qemu-img.c b/qemu-img.c
> index 80cfb9b..a514c17 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -33,6 +33,9 @@
>  #include <windows.h>
>  #endif
> 
> +#include "qint.h"
> +#include "qjson.h"
> +
>  typedef struct img_cmd_t {
>      const char *name;
>      int (*handler)(int argc, char **argv);
> @@ -84,6 +87,7 @@ static void help(void)
>             "  '-p' show progress of command (only certain commands)\n"
>             "  '-S' indicates the consecutive number of bytes that must contain only zeros\n"
>             "       for qemu-img to create a sparse image during conversion\n"
> +           "  '-j' try get json output, which would be in stdout, only valid in info command\n"

"try" makes it sound like this command can fail in some special way.  Instead, I suggest:

"  '--format=json' show output in machine-parsable JSON (only for info command)"


>             "\n"
>             "Parameters to check subcommand:\n"
>             "  '-r' tries to repair any inconsistencies that are found during the check.\n"
> @@ -1102,21 +1106,210 @@ static void dump_snapshots(BlockDriverState *bs)
>      g_free(sn_tab);
>  }
> 
> +/* string must be allocated on heap */
> +struct img_infos {
> +    char *filename;
> +    char *fmt;
> +    uint64_t total_sectors;
> +    int64_t allocated_size;
> +    int32 enc_flag;
> +    BlockDriverInfo *bdi;
> +    char *backing_filename;
> +    char *backing_filename_full;
> +    QEMUSnapshotInfo *sn_tab;
> +    int nb_sns;
> +};
> +
> +static void img_infos_init(struct img_infos *pinfo)
> +{
> +    memset(pinfo, 0, sizeof(struct img_infos));
> +}
> +
> +#define TRY_FREE(p) { \
> +    if ((p) != NULL) { \
> +        g_free((p)); \
> +        (p) = NULL; \
> +    } \
> +}

This is not necessary because free(NULL) is a nop.

Stefan

      parent reply	other threads:[~2012-07-30 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 10:20 [Qemu-devel] [PATCH] let qemu-img info genereate json output Wenchao Xia
2012-07-27 10:33 ` Daniel P. Berrange
2012-07-27 10:49   ` Paolo Bonzini
2012-07-27 10:52     ` Daniel P. Berrange
2012-07-27 13:52       ` Anthony Liguori
2012-07-27 13:50 ` Anthony Liguori
2012-08-15  8:49   ` Benoît Canet
2012-08-15 13:17     ` Eric Blake
2012-07-30 14:34 ` Stefan Hajnoczi [this message]

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=20120730143411.GB10211@stefanha-thinkpad.localdomain \
    --to=stefanha@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiawenc@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).