From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Borislav Petkov <bp@suse.de>,
Brendan Gregg <brendan.d.gregg@gmail.com>,
Chandler Carruth <chandlerc@gmail.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [GIT PULL 0/2] perf/core new features
Date: Sun, 25 Oct 2015 16:36:50 -0300 [thread overview]
Message-ID: <20151025193650.GK27006@kernel.org> (raw)
In-Reply-To: <20151025084607.GA24337@gmail.com>
Em Sun, Oct 25, 2015 at 09:46:07AM +0100, Ingo Molnar escreveu:
>
> * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>
> > Hi Ingo,
> >
> > Please consider pulling,
> >
> > - Arnaldo
> >
> > The following changes since commit 80fcd45ee05b4ef05e61d37a5ffb70a67095a9f6:
> >
> > Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core (2015-10-23 10:25:57 +0200)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo
> >
> > for you to fetch changes up to 161d9041782b86c5493481566539bfc058ceeaff:
> >
> > perf tools: Provide help for subset of options (2015-10-23 21:50:50 -0300)
> >
> > ----------------------------------------------------------------
> > perf/core improvements:
> >
> > New features:
> >
> > - Show ordered command line options when -h is used or when an
> > unknown option is specified (Arnaldo Carvalho de Melo)
> >
> > - If options are passed after -h, show just its descriptions, not
> > all options (Arnaldo Carvalho de Melo)
>
> Very nice!
>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > ----------------------------------------------------------------
> > Arnaldo Carvalho de Melo (2):
> > perf tools: Show tool command line options ordered
> > perf tools: Provide help for subset of options
> >
> > tools/perf/util/parse-options.c | 90 ++++++++++++++++++++++++++++++++++++-----
> > 1 file changed, 81 insertions(+), 9 deletions(-)
>
> Pulled, thanks a lot Arnaldo!
>
> So I tested this a bit, and the ordering works well.
>
> What wasn't so obvious to me was behavior like:
>
> triton:~/tip> perf report -h x
>
> Usage: perf report [<options>]
I'll fix that, and also make it search the provided key as a substring
in the event descriptions, like 'perf list' does now, does that sound ok?
- Arnaldo
>
> triton:~/tip>
>
> triton:~/tip> perf report -h exclude-other
>
> Usage: perf report [<options>]
>
>
> triton:~/tip>
>
> I.e. it outputs nothing and does not tell the user what's wrong.
>
> Then I figured out the right syntax:
>
> triton:~/tip> perf report -h --exclude-other
>
> Usage: perf report [<options>]
>
> -x, --exclude-other Only display entries with parent-match
>
> triton:~/tip>
>
> :)
>
> So maybe we should also try a search for the option name with a '-' and '--'
> prepended? Also, my pet peeve are partial matches:
>
> triton:~/tip> perf report -h --exclude
>
> Usage: perf report [<options>]
>
>
> triton:~/tip>
>
> But in any case it's a nice step forward!
>
> Ingo
prev parent reply other threads:[~2015-10-25 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 0:57 Arnaldo Carvalho de Melo
2015-10-24 0:57 ` [PATCH 1/2] perf tools: Show tool command line options ordered Arnaldo Carvalho de Melo
2015-10-24 0:57 ` [PATCH 2/2] perf tools: Provide help for subset of options Arnaldo Carvalho de Melo
2015-10-25 8:46 ` [GIT PULL 0/2] perf/core new features Ingo Molnar
2015-10-25 19:36 ` Arnaldo Carvalho de Melo [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=20151025193650.GK27006@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=bp@suse.de \
--cc=brendan.d.gregg@gmail.com \
--cc=chandlerc@gmail.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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
Powered by JetHome