From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Torsten Duwe <duwe@lst.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Julien Thierry <julien.thierry@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jiri Kosina <jikos@kernel.org>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
live-patching@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v8 0/5] arm64: ftrace with regs
Date: Mon, 21 Oct 2019 08:20:44 -0500 [thread overview]
Message-ID: <20191021132044.zkzclqtrexryyybl@treble> (raw)
In-Reply-To: <20191019130135.10de9324@blackhole.lan>
On Sat, Oct 19, 2019 at 01:01:35PM +0200, Torsten Duwe wrote:
> All calls going _out_ from the KLP module are newly generated, as part
> of the KLP module building process, and are thus aware of them being
> "extern" -- a PLT entry should be generated and accounted for in the
> KLP module.
Hm... for kpatch-build I assume we may need a GCC plugin to convert
local calls to global somehow?
--
Josh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-21 13:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 15:08 [PATCH v8 0/5] arm64: ftrace with regs Torsten Duwe
2019-02-08 15:10 ` [PATCH v8 1/5] arm64: replace -pg with CC_FLAGS_FTRACE in arm64 Makefiles Torsten Duwe
2019-02-11 11:53 ` Mark Rutland
2019-02-08 15:10 ` [PATCH v8 2/5] arm64: replace -pg with CC_FLAGS_FTRACE in efi Makefiles Torsten Duwe
2019-02-11 11:59 ` Mark Rutland
2019-04-08 15:23 ` Mark Rutland
2019-04-08 20:49 ` Ard Biesheuvel
2019-02-08 15:10 ` [PATCH v8 3/5] arm64: replace -pg with CC_FLAGS_FTRACE in mm/kasan Makefile Torsten Duwe
2019-02-11 11:55 ` Mark Rutland
2019-02-11 11:56 ` Mark Rutland
2019-04-08 15:25 ` Mark Rutland
2019-04-08 15:35 ` Andrey Ryabinin
2019-02-08 15:10 ` [PATCH v8 4/5] arm64: implement ftrace with regs Torsten Duwe
2019-02-13 10:30 ` Julien Thierry
2019-02-08 15:10 ` [PATCH v8 5/5] arm64: use -fpatchable-function-entry if available Torsten Duwe
2019-02-13 11:11 ` [PATCH v8 0/5] arm64: ftrace with regs Julien Thierry
2019-03-11 11:49 ` Torsten Duwe
2019-03-11 12:18 ` Mark Rutland
2019-03-29 10:18 ` Torsten Duwe
2019-04-08 15:36 ` Mark Rutland
2019-04-09 17:52 ` Will Deacon
2019-07-10 12:27 ` Ruslan Bilovol
2019-07-24 16:15 ` Mark Rutland
2019-10-16 11:42 ` Jiri Kosina
2019-10-16 17:58 ` Mark Rutland
2019-10-18 17:41 ` Mark Rutland
2019-10-19 11:01 ` Torsten Duwe
2019-10-21 11:37 ` Mark Rutland
2019-10-21 13:20 ` Josh Poimboeuf [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=20191021132044.zkzclqtrexryyybl@treble \
--to=jpoimboe@redhat.com \
--cc=amit.kachhap@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=duwe@lst.de \
--cc=jikos@kernel.org \
--cc=julien.thierry@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ruslan.bilovol@gmail.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.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).