All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] trace: move qemu_trace_opts to trace/control.c
Date: Thu, 19 May 2016 17:15:41 -0600	[thread overview]
Message-ID: <573E491D.2000009@redhat.com> (raw)
In-Reply-To: <1463473231-491-2-git-send-email-den@openvz.org>

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

On 05/17/2016 02:20 AM, Denis V. Lunev wrote:
> The patch also creates trace_opt_parse() helper in trace/control.c to reuse
> this code in next patches for qemu-nbd and qemu-io.
> 
> The patch also makes trace_init_events() static, as this call is not used
> outside the module anymore.
> 
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Paolo Bonzini <pbonzini@redhat.com>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Kevin Wolf <kwolf@redhat.com>
> ---
>  trace/control.c | 44 +++++++++++++++++++++++++++++++++++++++++++-
>  trace/control.h | 24 +++++++++++++-----------
>  vl.c            | 37 +------------------------------------
>  3 files changed, 57 insertions(+), 48 deletions(-)
> 
>  
> +QemuOptsList qemu_trace_opts = {
> +    .name = "trace",
> +    .implied_opt_name = "enable",
> +    .head = QTAILQ_HEAD_INITIALIZER(qemu_trace_opts.head),
> +    .desc = {
> +        {
> +            .name = "enable",
> +            .type = QEMU_OPT_STRING,
> +        },
> +        {
> +            .name = "events",
> +            .type = QEMU_OPT_STRING,
> +        },{

I know this is straight code motion, but we aren't very consistent on
spacing between elements.  Might be worth the extra newline here while
touching it?

> +            .name = "file",
> +            .type = QEMU_OPT_STRING,
> +        },
> +        { /* end of list */ }
> +    },
> +};

Reviewed-by: Eric Blake <eblake@redhat.com>

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

  reply	other threads:[~2016-05-19 23:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17  8:20 [Qemu-devel] [PATCH 0/3] trace: enable tracing in qemu-io/qemu-nbd Denis V. Lunev
2016-05-17  8:20 ` [Qemu-devel] [PATCH 1/3] trace: move qemu_trace_opts to trace/control.c Denis V. Lunev
2016-05-19 23:15   ` Eric Blake [this message]
2016-05-17  8:20 ` [Qemu-devel] [PATCH 2/3] trace: enable tracing in qemu-io Denis V. Lunev
2016-05-19 23:23   ` Eric Blake
2016-05-17  8:20 ` [Qemu-devel] [PATCH 3/3] trace: enable tracing in qemu-nbd Denis V. Lunev
2016-05-19 23:26   ` Eric Blake
2016-05-31  8:50     ` Denis V. Lunev
2016-05-17 12:40 ` [Qemu-devel] [PATCH 0/3] trace: enable tracing in qemu-io/qemu-nbd Paolo Bonzini
2016-05-27 20:39 ` Stefan Hajnoczi
2016-05-27 20:42   ` Denis V. Lunev
  -- strict thread matches above, loose matches on Subject: below --
2016-05-31  8:58 [Qemu-devel] [PATCH v2 " Denis V. Lunev
2016-05-31  8:58 ` [Qemu-devel] [PATCH 1/3] trace: move qemu_trace_opts to trace/control.c Denis V. Lunev

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=573E491D.2000009@redhat.com \
    --to=eblake@redhat.com \
    --cc=den@openvz.org \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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.