From: abelvesa@gmail.com (Abel Vesa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS
Date: Thu, 9 Feb 2017 18:18:15 +0000 [thread overview]
Message-ID: <20170209181815.GA3439@nuc> (raw)
In-Reply-To: <20170209180644.GJ27312@n2100.armlinux.org.uk>
On Thu, Feb 09, 2017 at 06:06:44PM +0000, Russell King - ARM Linux wrote:
> On Thu, Feb 09, 2017 at 12:13:22PM -0500, Steven Rostedt wrote:
> > Then came along live kernel patching, which I believe this series is
> > trying to support. What is needed by pt_regs is a way to "hijack" the
> > function being called to instead call the patched function. That is,
> > ftrace is not being used for tracing, but in reality, being used to
> > modify the running kernel. It is being used to change what function
> > gets called. ftrace is just a hook for that mechanism.
>
> So, would I be correct to assume that the only parts of pt_regs that
> would be touched are those which contain arguments to the function,
> and the register which would contain the return value?
At this point, yeah, but I intend to come up with another patch series
for livepatching which needs the exact same context as the function
livepatched. This means all the regs need to be saved and restored
before calling the replacing function.
>
> --
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
> according to speedtest.net.
next prev parent reply other threads:[~2017-02-09 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 22:57 [PATCHv3] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS Abel Vesa
2017-02-09 15:38 ` Jean-Jacques Hiblot
2017-02-09 15:49 ` Russell King - ARM Linux
2017-02-09 16:29 ` Russell King - ARM Linux
2017-02-09 17:13 ` Steven Rostedt
2017-02-09 18:06 ` Russell King - ARM Linux
2017-02-09 18:14 ` Steven Rostedt
2017-02-09 18:14 ` Steven Rostedt
2017-02-09 19:01 ` Abel Vesa
2017-02-09 19:09 ` Abel Vesa
2017-02-09 18:18 ` Abel Vesa [this message]
2017-02-09 18:30 ` Abel Vesa
2017-02-10 10:36 ` Jean-Jacques Hiblot
2017-02-10 12:03 ` Abel Vesa
2017-02-10 13:57 ` Jean-Jacques Hiblot
2017-02-10 17:27 ` Abel Vesa
2017-02-10 14:28 ` Russell King - ARM Linux
2017-02-10 17:17 ` Abel Vesa
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=20170209181815.GA3439@nuc \
--to=abelvesa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).