From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2 4/4] perf: Support perf -vv
Date: Thu, 29 Mar 2018 08:52:32 +0800 [thread overview]
Message-ID: <e0682929-5cc1-386e-fb53-e8971469e61c@linux.intel.com> (raw)
In-Reply-To: <20180328154622.65ate24g7be2xg3a@gmail.com>
On 3/28/2018 11:46 PM, Ingo Molnar wrote:
>
> * Jin Yao <yao.jin@linux.intel.com> wrote:
>
>> $ ./perf -vv or ./perf -version --build-options
>> perf version 4.13.rc5.gcb1183
>
> My suggestion was to add the 'version' subcommand like Git has, not a "-version"
> option:
>
> $ git version
> git version 2.14.1
>
> Thanks,
>
> Ingo
>
Hi Ingo,
Sorry about that. Actually I find it's a bug in my patch. The 'perf
-vxyz' is mapped to 'perf --version' mistakenly. So 'perf -version' will
be mapped to 'perf --version' and 'perf -vabc' will be mapped too.
I will fix this bug.
Currently, 'perf -v', 'perf version' and 'perf --version' have the same
behavior.
So I will let:
'perf -v --build-options',
'perf version --build-options',
'perf --version --build-options',
'perf -vv'
have same output.
For example,
$ ./perf version --build-options
perf version 4.13.rc5.gcb1183
dwarf: [ on ]
dwarf_getlocations: [ on ]
glibc: [ on ]
gtk2: [ on ]
libaudit: [ OFF ]
libbfd: [ on ]
libelf: [ on ]
libnuma: [ on ]
numa_num_possible_cpus: [ on ]
libperl: [ on ]
libpython: [ on ]
libslang: [ on ]
libcrypto: [ on ]
libunwind: [ on ]
libdw-dwarf-unwind: [ on ]
zlib: [ on ]
lzma: [ on ]
get_cpuid: [ on ]
bpf: [ on ]
Thanks
Jin Yao
prev parent reply other threads:[~2018-03-29 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:57 [PATCH v2 0/4] Support perf -vv Jin Yao
2018-03-28 14:57 ` [PATCH v2 1/4] tools include: Add config.h header file Jin Yao
2018-03-28 14:57 ` [PATCH v2 3/4] perf version: Print the compiled-in status of libraries Jin Yao
2018-03-28 13:10 ` Jiri Olsa
2018-03-28 13:57 ` Jin, Yao
2018-03-28 14:57 ` [PATCH v2 4/4] perf: Support perf -vv Jin Yao
2018-03-28 13:22 ` Jiri Olsa
2018-03-28 14:00 ` Jin, Yao
2018-03-28 14:19 ` Jiri Olsa
2018-03-28 14:56 ` Jin, Yao
2018-03-28 15:46 ` Ingo Molnar
2018-03-29 0:52 ` Jin, Yao [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=e0682929-5cc1-386e-fb53-e8971469e61c@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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.