From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] trace: enable trace events in qemu-img
Date: Tue, 31 May 2016 14:23:15 +0100 [thread overview]
Message-ID: <20160531132315.GT21628@redhat.com> (raw)
In-Reply-To: <574D887C.7010806@redhat.com>
On Tue, May 31, 2016 at 06:50:04AM -0600, Eric Blake wrote:
> On 05/31/2016 04:07 AM, Denis V. Lunev wrote:
> > The command will work this way:
> > qemu-img create --trace qcow2* -f qcow2 1.img 64G
> >
> > Signed-off-by: Denis V. Lunev <den@openvz.org>
> > Suggested by: Daniel P. Berrange <berrange@redhat.com>
> > CC: Eric Blake <eblake@redhat.com>
> > CC: Paolo Bonzini <pbonzini@redhat.com>
> > CC: Stefan Hajnoczi <stefanha@redhat.com>
> > CC: Kevin Wolf <kwolf@redhat.com>
> > ---
> > qemu-img.c | 97 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 96 insertions(+), 1 deletion(-)
>
> Missing man page additions.
>
>
> > @@ -155,7 +157,12 @@ static void QEMU_NORETURN help(void)
> > "Parameters to compare subcommand:\n"
> > " '-f' first image format\n"
> > " '-F' second image format\n"
> > - " '-s' run in Strict mode - fail on different image size or sector allocation\n";
> > + " '-s' run in Strict mode - fail on different image size or sector allocation\n"
> > + "\n"
> > + "General purpose options:\n"
> > + " -R, --trace [[enable=]<pattern>][,events=<file>][,file=<file>]\n"
> > + " specify tracing options\n"
> > + " see qemu(1) man page for full description\n";
>
> Why -R? Because -T is already in use by rebase and compare? I'd almost
> rather have _just_ --trace with no short option, than to pick yet
> another letter, but you might want to wait for other opinions first.
Agreed, I think it'd be fine to use --trace and skip the short option
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-05-31 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 10:07 [Qemu-devel] [PATCH 4/4] trace: enable trace events in qemu-img Denis V. Lunev
2016-05-31 12:50 ` Eric Blake
2016-05-31 12:55 ` Denis V. Lunev
2016-05-31 13:23 ` Daniel P. Berrange [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=20160531132315.GT21628@redhat.com \
--to=berrange@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--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 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).