From: Wang Nan <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
<linux-kernel@vger.kernel.org>, <zhangzhiqiang.zhang@huawei.com>,
<peifeiyue@huawei.com>
Subject: Re: [PATCH] perf tools: fix incorrect header string
Date: Thu, 16 Oct 2014 11:21:13 +0800 [thread overview]
Message-ID: <543F39A9.3030308@huawei.com> (raw)
In-Reply-To: <20141015151358.GK3198@kernel.org>
On 2014/10/15 23:13, Arnaldo Carvalho de Melo wrote:
> Em Wed, Oct 15, 2014 at 11:28:53AM +0800, Wang Nan escreveu:
>> Commit fbe96f29 (perf tools: Make perf.data more self-descriptive)
>> read '/proc/cpuinfo' to form cpu descriptor. For ARM, it finds
>> 'Processor' field. It is correct when the patch merged, but due to
>> commit b4b8f770 (ARM: kernel: update cpuinfo to print all online CPUs
>> features), the corresponding information becomes 'model name' field.
>>
>> This patch simply corrects it.
>
> It doesn't :-)
>
> It makes it work with kernels >= b4b8f770, and fail with older kernels.
>
> We need to somehow figure out where the right information is regardless
> of the kernel.
>
> - Arnaldo
>
However it is a real problem. Look at output on arm platform at the
bottom of this mail, especially "cpudesc", "total memory" and "cmdline" field.
By further debugging I found that the real problem resides in return value checking
when write header error. Please see my other patches:
https://lkml.org/lkml/2014/10/15/612
https://lkml.org/lkml/2014/10/15/611
I think at least one of them is required.
Thanks.
>> Signed-off-by: Wang Nan <wangnan0@huawei.com>
>> ---
>> tools/perf/perf-sys.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/perf-sys.h b/tools/perf/perf-sys.h
>> index 937e432..4293970 100644
>> --- a/tools/perf/perf-sys.h
>> +++ b/tools/perf/perf-sys.h
>> @@ -113,7 +113,7 @@
>> #define mb() ((void(*)(void))0xffff0fa0)()
>> #define wmb() ((void(*)(void))0xffff0fa0)()
>> #define rmb() ((void(*)(void))0xffff0fa0)()
>> -#define CPUINFO_PROC "Processor"
>> +#define CPUINFO_PROC "model name"
>> #endif
>>
>> #ifdef __aarch64__
>> --
>> 1.8.4
bash-4.2# perf record ls
...
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.001 MB perf.data (~36 samples) ]
bash-4.2# perf report --stdio --header
Error:
The perf.data file has no samples!
# ========
# captured on: Fri Sep 12 10:09:10 2014
# hostname : arma15el
# os release : 3.17.0+
# perf version : 3.10.53
# arch : armv7l
# nrcpus online : 4
# nrcpus avail : 1
# cpudesc : (null)
# total memory : 0 kB
# cmdline :
# event : name = cycles, type = 0, config = 0x0, config1 = 0x0, config2 = 0x0, excl_usr = 0, excl_kern = 0, excl_host = 0, excl_guest = 1, precise_ip = 0
# pmu mappings: not available
# ========
#
next prev parent reply other threads:[~2014-10-16 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 3:28 [PATCH] perf tools: fix incorrect header string Wang Nan
2014-10-15 15:13 ` Arnaldo Carvalho de Melo
2014-10-16 3:21 ` Wang Nan [this message]
2014-10-16 14:55 ` Arnaldo Carvalho de Melo
2014-10-21 3:56 ` Wang Nan
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=543F39A9.3030308@huawei.com \
--to=wangnan0@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peifeiyue@huawei.com \
--cc=zhangzhiqiang.zhang@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