From: Jean-Jacques Hiblot <jjhiblot@traphandler.com>
To: jslaby@suse.cz, linux@arm.linux.org.uk, rostedt@goodmis.org,
mingo@redhat.com, nsekhar@ti.com,
stefano.stabellini@eu.citrix.com, christoffer.dall@linaro.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jean-Jacques Hiblot <jjhiblot@traphandler.com>
Subject: [PATCH] arm: ftrace: Adds support for ftrace operations
Date: Fri, 7 Nov 2014 15:59:11 +0100 [thread overview]
Message-ID: <1415372352-15664-1-git-send-email-jjhiblot@traphandler.com> (raw)
Hi all,
This patch adds support for ftrace operations on the ARM architecture.
This support is needed by kgraft and possibly other ftrace-based tools.
My goal is to have kgraft working on ARM and aarch64.
I tested this patch with a toy implementation of kgraft for ARM and basic
usage of function and function_graph tracers
It doesn't show any problem with the ftrace selftests and the tests found
today in branch ftrace/testing-mystuff of linux-trace repository
(git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git)
Jean-Jacques Hiblot (1):
arm: ftrace: Adds support for ftrace operations
arch/arm/Kconfig | 2 ++
arch/arm/include/asm/ftrace.h | 3 ++
arch/arm/kernel/entry-common.S | 68 +++++++++++++++++++++++++++++++++++++++++-
arch/arm/kernel/ftrace.c | 34 +++++++++++++++++++++
4 files changed, 106 insertions(+), 1 deletion(-)
--
2.1.3
next reply other threads:[~2014-11-07 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 14:59 Jean-Jacques Hiblot [this message]
2014-11-07 14:59 ` [PATCH 01/01] " Jean-Jacques Hiblot
2014-11-07 16:52 ` [PATCH] " Steven Rostedt
2014-11-07 17:01 ` Jean-Jacques Hiblot
2014-11-24 9:59 ` Jean-Jacques Hiblot
2014-11-25 23:20 ` Steven Rostedt
2014-11-27 10:23 ` Jean-Jacques Hiblot
2014-11-27 14:58 ` Steven Rostedt
2014-11-10 8:56 ` [PATCH v2 00/01] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS Jean-Jacques Hiblot
2014-11-10 8:56 ` [PATCH v2 01/01] " Jean-Jacques Hiblot
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=1415372352-15664-1-git-send-email-jjhiblot@traphandler.com \
--to=jjhiblot@traphandler.com \
--cc=christoffer.dall@linaro.org \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=nsekhar@ti.com \
--cc=rostedt@goodmis.org \
--cc=stefano.stabellini@eu.citrix.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
all inboxes | Powered by JetHome®