From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 1/2] trace: document how to specify multiple --trace patterns
Date: Mon, 15 Feb 2021 12:39:25 +0100 [thread overview]
Message-ID: <20210215113925.GI7226@merkur.fritz.box> (raw)
In-Reply-To: <20210113141517.GB255928@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 3478 bytes --]
Am 13.01.2021 um 15:15 hat Stefan Hajnoczi geschrieben:
> On Wed, Jan 13, 2021 at 01:51:17PM +0100, BALATON Zoltan wrote:
> > On Wed, 13 Jan 2021, Stefan Hajnoczi wrote:
> > > On Tue, Jan 12, 2021 at 09:44:03PM +0100, BALATON Zoltan wrote:
> > > > On Tue, 12 Jan 2021, Stefan Hajnoczi wrote:
> > > > > It is possible to repeat the --trace option to specify multiple
> > > > > patterns. This may be preferrable to users who do not want to create a
> > > > > file with a list of patterns.
> > > > >
> > > > > Suggested-by: BALATON Zoltan <balaton@eik.bme.hu>
> > > > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > > > ---
> > > > > docs/devel/tracing.rst | 9 +++++++--
> > > > > 1 file changed, 7 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/docs/devel/tracing.rst b/docs/devel/tracing.rst
> > > > > index 4ebf8e38ea..8777c19d14 100644
> > > > > --- a/docs/devel/tracing.rst
> > > > > +++ b/docs/devel/tracing.rst
> > > > > @@ -22,10 +22,15 @@ events::
> > > > > This output comes from the "log" trace backend that is enabled by default when
> > > > > ``./configure --enable-trace-backends=BACKENDS`` was not explicitly specified.
> > > > >
> > > > > -More than one trace event pattern can be specified by providing a file
> > > > > -instead::
> > > > > +Multiple patterns can be specified by repeating the ``--trace`` option::
> > > > > +
> > > > > + $ qemu --trace "kvm_*" --trace "virtio_*" ...
> > > >
> > > > QEMU options are single dash with double dash accepted for compatibility but
> > > > help and other docs have single dash so these (and below) should be -trace.
> > > > (Also a bit less typing for otherwise already way too long command lines.)
> > >
> > > Is this documented somewhere?
> >
> > Maybe qemu-system-* -help ?
>
> I mean developer documentation like CODING_STYLE.rst so we can point to
> that when someone submits a patch that does not use the preferred
> syntax.
>
> > > I was under the impression that '-' is legacy syntax and '--' is the
> > > preferred syntax. There are examples of '--' on the QEMU man page.
> >
> > -- is also accepted but they are the same as single dash options. Some tools
> > may have -- syntax preferred but not QEMU itself. If so that may be an
> > inconsistency.
> >
> > > Let's reach agreement, document it, and then make the documentation
> > > consistent.
> >
> > Since we don't have long and short arguments for the same options (like
> > -m,--memory) I think -- does not make much sense. Also single dash is less
> > typing and there are other programs using the same convention (e.g. whole X
> > Window System) so I think the current one dash options are fine and should
> > be kept consistent. As long as we can agree on this I can agree with that.
> > :-)
>
> I'm fine with either (or even using both interchangeably) but want to
> make sure it's agreed for all of QEMU so we can really follow it and
> don't need to spend time on it in the future.
>
> Kevin: You used '--' in qemu-storage-daemon --help. Does this mean you
> want QEMU to stop using '-'?
qemu-storage-daemon just follows the example of the other tools which
use getopt() instead of a hand-written parser, which means that in all
of the tools, long options require '--'.
I don't have a strong opinion about '-' in the system emulator, though
if I tried out dropping it, I guess I'd find my muscle memory does have
one.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-15 11:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:58 [PATCH 0/2] trace: documentation improvements Stefan Hajnoczi
2021-01-12 16:58 ` [PATCH 1/2] trace: document how to specify multiple --trace patterns Stefan Hajnoczi
2021-01-12 18:50 ` Philippe Mathieu-Daudé
2021-01-12 20:44 ` BALATON Zoltan
2021-01-13 9:48 ` Stefan Hajnoczi
[not found] ` <afd6945e-2666-1b80-70c8-27564cf5ac5@eik.bme.hu>
2021-01-13 14:15 ` Stefan Hajnoczi
2021-02-15 11:39 ` Kevin Wolf [this message]
2021-01-13 21:42 ` John Snow
2021-01-13 22:15 ` Eric Blake
2021-01-13 23:08 ` John Snow
2021-01-13 23:45 ` BALATON Zoltan
2021-01-14 0:20 ` John Snow
2021-01-14 14:02 ` Stefan Hajnoczi
2021-01-14 14:18 ` BALATON Zoltan
2021-01-14 16:44 ` Stefan Hajnoczi
2021-01-19 16:31 ` Eric Blake
2021-02-01 11:22 ` Stefan Hajnoczi
2021-01-14 17:22 ` John Snow
2021-01-12 16:58 ` [PATCH 2/2] trace: update docs with meson build information Stefan Hajnoczi
2021-02-01 11:23 ` [PATCH 0/2] trace: documentation improvements Stefan Hajnoczi
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=20210215113925.GI7226@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@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).