From: Chulmin Kim <cmkim@core.kaist.ac.kr>
To: linux-perf-users@vger.kernel.org
Subject: Re: Does Perf support AMD cpu perfectly?
Date: Tue, 27 Nov 2012 15:42:31 +0900 [thread overview]
Message-ID: <50B460D7.4080804@core.kaist.ac.kr> (raw)
In-Reply-To: <50B3743C.5020508@core.kaist.ac.kr>
Update for this issue.
The patchset works correctly.
Now the problem is the number of the events to be monitored.
I will start a new thread for this issue.
Thanks.
2012-11-26 오후 10:53, Chulmin Kim 쓴 글:
> Sorry for the posting with no patience.
>
> I've found the patch. (https://patchwork.kernel.org/patch/1722691/)
>
> It's pretty new. (released on 10,nov,2012)
>
> If you have something to mention about this issue,
>
> don't hesitate to contact me.
>
> Thanks.
>
> 2012-11-26 오후 10:45, Chulmin Kim 쓴 글:
>> Update for this issue.
>>
>> I'm investigating the kernel source.
>>
>> I found that Perf for AMD seems imperfect in linux 3.0 (my machine's
>> linux version).
>>
>> For AMD family 15h, there is a commented line as follow.
>> - /* nortbridge counters not yet implemented: */ (line 541,
>> perf_event_amd.c )
>>
>>
>> According to my further exploration, linux 3.2 does not support it either.
>>
>> Does any of you know or have the patch for it?
>>
>>
>> 2012-11-26 오후 9:15, Chulmin Kim 쓴 글:
>>> Update for this issue.
>>>
>>> - rc0 and instruction events show the similar result.
>>> - still, the count of L3 cache miss event is 1/10 of what i expected.
>>> (LLC-load-misses)
>>>
>>>
>>>
>>> 2012-11-26 오후 8:24, Chulmin Kim 쓴 글:
>>>> Hi all.
>>>>
>>>> I'm on the way of monitoring AMD machine.
>>>>
>>>> I wonder Perf is supporting AMD PMU Events perfectly or not.
>>>>
>>>> It seems not working correctly despite the same command works in intel
>>>> machines perfectly.
>>>>
>>>> command : (perf stat -e rc0 -e instructions ./blah)
>>>> result : the value for "rc0" almost equals to that of "instruction" in
>>>> Intel machine, while it does not in AMD machine
>>>>
>>>>
>>>> Other events such as cache events seem weird also.
>>>>
>>>> Is there any material mentioning this issue?
>>>>
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-11-27 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 11:24 Does Perf support AMD cpu perfectly? Chulmin Kim
2012-11-26 12:15 ` Chulmin Kim
2012-11-26 13:45 ` Chulmin Kim
2012-11-26 13:53 ` Chulmin Kim
2012-11-27 6:42 ` Chulmin Kim [this message]
2012-11-26 14:05 ` Jiri Olsa
2012-11-26 15:43 ` Chulmin Kim
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=50B460D7.4080804@core.kaist.ac.kr \
--to=cmkim@core.kaist.ac.kr \
--cc=linux-perf-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).