[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e0682929-5cc1-386e-fb53-e8971469e61c@linux.intel.com>
Date: Thu, 29 Mar 2018 08:52:32 +0800
From: "Jin, Yao" <yao.jin@...ux.intel.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: acme@...nel.org, jolsa@...nel.org, peterz@...radead.org,
mingo@...hat.com, alexander.shishkin@...ux.intel.com,
Linux-kernel@...r.kernel.org, ak@...ux.intel.com,
kan.liang@...el.com, yao.jin@...el.com
Subject: Re: [PATCH v2 4/4] perf: Support perf -vv
On 3/28/2018 11:46 PM, Ingo Molnar wrote:
>
> * Jin Yao <yao.jin@...ux.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
Powered by blists - more mailing lists