From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] arm64: ftrace: emit ftrace-mod.o contents through code
Date: Tue, 28 Nov 2017 18:31:21 +0000 [thread overview]
Message-ID: <20171128183121.GN9266@arm.com> (raw)
In-Reply-To: <20171120174130.28626-2-ard.biesheuvel@linaro.org>
On Mon, Nov 20, 2017 at 05:41:30PM +0000, Ard Biesheuvel wrote:
> When building the arm64 kernel with both CONFIG_ARM64_MODULE_PLTS and
> CONFIG_DYNAMIC_FTRACE enabled, the ftrace-mod.o object file is built
> with the kernel and contains a trampoline that is linked into each
> module, so that modules can be loaded far away from the kernel and
> still reach the ftrace entry point in the core kernel with an ordinary
> relative branch, as is emitted by the compiler instrumentation code
> dynamic ftrace relies on.
>
> In order to be able to build out of tree modules, this object file
> needs to be included into the linux-headers or linux-devel packages,
> which is undesirable, as it makes arm64 a special case (although a
> precedent does exist for 32-bit PPC).
>
> Given that the trampoline essentially consists of a PLT entry, let's
> not bother with a source or object file for it, and simply patch it
> in whenever the trampoline is being populated, using the existing
> PLT support routines.
I'll pick these two up for 4.15. Do you think they need to go to stable as
well?
Will
next prev parent reply other threads:[~2017-11-28 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 17:41 [PATCH v3 1/2] arm64: module-plts: factor out PLT generation code for ftrace Ard Biesheuvel
2017-11-20 17:41 ` [PATCH v3 2/2] arm64: ftrace: emit ftrace-mod.o contents through code Ard Biesheuvel
2017-11-28 18:31 ` Will Deacon [this message]
2017-11-28 18:37 ` Ard Biesheuvel
2017-12-01 11:55 ` Riku Voipio
2017-11-28 18:30 ` [PATCH v3 1/2] arm64: module-plts: factor out PLT generation code for ftrace Will Deacon
2017-11-28 18:41 ` Ard Biesheuvel
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=20171128183121.GN9266@arm.com \
--to=will.deacon@arm.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).