[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52AF2537.1030007@cn.fujitsu.com>
Date: Mon, 16 Dec 2013 11:07:19 -0500
From: Dongsheng Yang <yangds.fnst@...fujitsu.com>
To: Ramkumar Ramachandra <artagnon@...il.com>
CC: David Ahern <dsahern@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH] perf list: fix --raw-dump
On 12/12/2013 02:34 AM, Ramkumar Ramachandra wrote:
> David Ahern wrote:
>> Why not make raw_dump a proper argument?
> Sure, that'd work too. I was thinking of a minimal way to fix the
> problem myself.
Hi Ramkumar and David,
If this argument is only used for perf complement, how about make
it hidden to user? Please refer https://lkml.org/lkml/2013/12/12/52 and
https://lkml.org/lkml/2013/12/12/53 The two patches make --raw-dump used
internally but hidden in output of '-h'.
If you think we should expose it to user, I think we should make it
work as an option rather than an argument, and make the output of it
more readable,
how about the patch attached in this mail?
Example:
# ./perf list cache --raw-dump
L1-dcache-loads
L1-dcache-load-misses
L1-dcache-stores
L1-dcache-store-misses
L1-dcache-prefetch-misses
L1-icache-load-misses
LLC-loads
LLC-stores
LLC-prefetches
dTLB-loads
dTLB-load-misses
dTLB-stores
dTLB-store-misses
iTLB-loads
iTLB-load-misses
branch-loads
branch-load-misses
View attachment "0001-perf-list-Fix-raw-dump-arg.patch" of type "text/x-patch" (6382 bytes)
Powered by blists - more mailing lists