From: Catalin Marinas <catalin.marinas@arm.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Robert Richter <rric@kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
"huxinwei@huawei.com" <huxinwei@huawei.com>
Subject: Re: [PATCH] arm64: add OProfile support
Date: Sat, 26 Apr 2014 10:23:05 +0100 [thread overview]
Message-ID: <58ED971B-CC04-4BE1-916C-386D219874A8@arm.com> (raw)
In-Reply-To: <535B707F.7020802@huawei.com>
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
next prev parent reply other threads:[~2014-04-26 9:23 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 [this message]
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
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=58ED971B-CC04-4BE1-916C-386D219874A8@arm.com \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dingtianhong@huawei.com \
--cc=huxinwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oprofile-list@lists.sf.net \
--cc=paulus@samba.org \
--cc=rric@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).