From: William Cohen <wcohen@redhat.com>
To: Ding Tianhong <dingtianhong@huawei.com>,
William Cohen <wcohen@nc.rr.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linuxarm@huawei.com, "huxinwei@huawei.com" <huxinwei@huawei.com>,
Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
Stephane Eranian <eranian@gmail.com>,
Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: [PATCH] arm64: add OProfile support
Date: Mon, 05 May 2014 15:55:04 -0400 [thread overview]
Message-ID: <5367EC98.6090409@redhat.com> (raw)
In-Reply-To: <53674615.5000509@huawei.com>
On 05/05/2014 04:04 AM, Ding Tianhong wrote:
> On 2014/4/29 4:39, William Cohen wrote:
>> On 04/27/2014 10:32 PM, Ding Tianhong wrote:
>>> On 2014/4/26 18:22, Ding Tianhong wrote:
>>>> On 2014/4/26 17:23, Catalin Marinas wrote:
>>>>> On 26 Apr 2014, at 09:38, Ding Tianhong <dingtianhong@huawei.com> wrote:
>>>>>> Add OProfile support for arm64, using the perf backend, and failing back
>>>>>> to generic timer based sampling if PMU interrupt is not supported.
>>>>>>
>>>>>> I have test this patch on Cortex-A53 and Cortex-A57 motherboard, the OProfile
>>>>>> could work well by PMU irq or arch timer irq.
>>>>>
>>>>> This came up before a few times and we also had an implementation but
>>>>> decided not to merge it. We should rather get the user space oprofile to
>>>>> use the perf kernel API.
>>>>>
>>>>> That’s an old thread, it may have even made it into mainline oprofile
>>>>> but I haven’t followed the development:
>>>>>
>>>>> http://marc.info/?l=oprofile-list&m=133002515616302&w=2
>>>>>
>>>>> Catalin
>>>>>
>>>
>>> Hi Cadtalin:
>>>
>>> Sorry I could not find the implementation that not to merge the orpfile support for aarch64 till now, and
>>> I still have questions that the existing code only support oprofile by arch timer event, but not
>>> PMU event, this patch only add HW PMU support for oprofile, it is more accurate and stable, can you
>>> give me more advise and appreciate for your help.
>>>
>>> Regards
>>> Ding
>>
>> Hi Ding,
>>
>> There is some basic support for arm64 in oprofile using the kernel's perf infrastructure for the Applied Micro X-Gene processor checked into the upstream oprofile git repository:
>>
>> http://sourceforge.net/p/oprofile/oprofile/ci/34d0065a1a790fc2be05a5ef1d8b0bbf28b814fe/
>>
>> It should be straight forward to adapt and extend this to work for A53 and A57 processors in libop/op_cpu_type.c. At the time I didn't have access to the cortex a57/a53 documentation so this was implemented for the the base ARMv8 PMUv3 events. The processor identification for Cortex a53 and a57 will also need to be added. to /libop/op_cpu_type.c. I don't currently have access to cortex a53 or a57 processors, so I don't know what the magic vendorid and cpuid values are. What is the output of "cat /proc/cpuinfo" for each of the aarch64 processors you are running oprofile on?
>>
>> -Will
>>
>
> Hi Will:
>
> Sorry for feedback so late, too busy these days. :)
>
> Thanks for your message, you can add the the A53 and A57 to support arm-v8 for oprofile.
>
> A53 A57
> Vendid 0x41 0x41
> cpuid 0xD03 0xD07
>
> -Ding
Hi Ding,
Thanks very much for the IDs for Cortex A53 and Cortex A57.
-Will
prev parent reply other threads:[~2014-05-05 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 8:38 [PATCH] arm64: add OProfile support Ding Tianhong
2014-04-26 9:23 ` Catalin Marinas
2014-04-26 10:22 ` Ding Tianhong
2014-04-28 2:32 ` Ding Tianhong
2014-04-28 19:08 ` Will Deacon
[not found] ` <535EBC96.3090008@nc.rr.com>
2014-05-05 8:04 ` Ding Tianhong
2014-05-05 19:55 ` William Cohen [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=5367EC98.6090409@redhat.com \
--to=wcohen@redhat.com \
--cc=Will.Deacon@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=catalin.marinas@arm.com \
--cc=dingtianhong@huawei.com \
--cc=eranian@gmail.com \
--cc=huxinwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mingo@redhat.com \
--cc=oprofile-list@lists.sf.net \
--cc=paulus@samba.org \
--cc=vincent.weaver@maine.edu \
--cc=wcohen@nc.rr.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;
as well as URLs for NNTP newsgroup(s).