From: duwe@lst.de (Torsten Duwe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] arm64: implement ftrace with regs
Date: Wed, 31 Oct 2018 18:58:00 +0100 [thread overview]
Message-ID: <20181031185800.6aa17c91@blackhole> (raw)
In-Reply-To: <20181031141819.lv2tuj4ne5nf3lh3@lakrids.cambridge.arm.com>
On Wed, 31 Oct 2018 14:18:19 +0000
Mark Rutland <mark.rutland@arm.com> wrote:
> On Wed, Oct 31, 2018 at 02:19:07PM +0100, Jiri Kosina wrote:
> > Other architectures do rely on that. That's exactly for example why
> > on x86 we use '-pg -mfentry', to make sure we hook the function
> > *before* prologue.
>
> Ah, I'd missed -mfentry for x86. I now see that's also the case with
> __gnu_mcount_nc on arch/arm, so that covers my confusion.
Yes, fentry used to be the prerequisite, but it's everything but
portable. PPC64 already had the profile-kernel switch, which was
becoming just usable as we got at live patching.
I'm hoping that the patchable-function-entry will become the future
de-facto standard.
Torsten
WARNING: multiple messages have this Message-ID (diff)
From: Torsten Duwe <duwe@lst.de>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Jiri Kosina <jikos@kernel.org>, Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Julien Thierry <julien.thierry@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
kristina.martsenko@arm.com
Subject: Re: [PATCH v4 1/3] arm64: implement ftrace with regs
Date: Wed, 31 Oct 2018 18:58:00 +0100 [thread overview]
Message-ID: <20181031185800.6aa17c91@blackhole> (raw)
In-Reply-To: <20181031141819.lv2tuj4ne5nf3lh3@lakrids.cambridge.arm.com>
On Wed, 31 Oct 2018 14:18:19 +0000
Mark Rutland <mark.rutland@arm.com> wrote:
> On Wed, Oct 31, 2018 at 02:19:07PM +0100, Jiri Kosina wrote:
> > Other architectures do rely on that. That's exactly for example why
> > on x86 we use '-pg -mfentry', to make sure we hook the function
> > *before* prologue.
>
> Ah, I'd missed -mfentry for x86. I now see that's also the case with
> __gnu_mcount_nc on arch/arm, so that covers my confusion.
Yes, fentry used to be the prerequisite, but it's everything but
portable. PPC64 already had the profile-kernel switch, which was
becoming just usable as we got at live patching.
I'm hoping that the patchable-function-entry will become the future
de-facto standard.
Torsten
next prev parent reply other threads:[~2018-10-31 17:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 14:20 [PATCH v4 0/3] arm64 live patching Torsten Duwe
2018-10-26 14:20 ` Torsten Duwe
2018-10-26 14:21 ` [PATCH v4 1/3] arm64: implement ftrace with regs Torsten Duwe
2018-10-26 14:21 ` Torsten Duwe
2018-10-31 12:10 ` Mark Rutland
2018-10-31 12:10 ` Mark Rutland
2018-10-31 13:19 ` Jiri Kosina
2018-10-31 13:19 ` Jiri Kosina
2018-10-31 14:18 ` Mark Rutland
2018-10-31 14:18 ` Mark Rutland
2018-10-31 17:58 ` Torsten Duwe [this message]
2018-10-31 17:58 ` Torsten Duwe
2018-11-08 12:12 ` Ard Biesheuvel
2018-11-08 12:12 ` Ard Biesheuvel
2018-11-12 11:51 ` Torsten Duwe
2018-11-12 11:51 ` Torsten Duwe
2018-10-26 14:21 ` [PATCH v4 2/3] arm64: implement live patching Torsten Duwe
2018-10-26 14:21 ` Torsten Duwe
2018-11-06 16:49 ` Miroslav Benes
2018-11-06 16:49 ` Miroslav Benes
2018-11-08 12:42 ` Ard Biesheuvel
2018-11-08 12:42 ` Ard Biesheuvel
2018-11-12 11:01 ` Torsten Duwe
2018-11-12 11:01 ` Torsten Duwe
2018-11-12 11:06 ` Ard Biesheuvel
2018-11-12 11:06 ` Ard Biesheuvel
2018-10-26 14:21 ` [PATCH v4 3/3] arm64: reliable stacktraces Torsten Duwe
2018-10-26 14:21 ` Torsten Duwe
2018-10-26 15:37 ` Josh Poimboeuf
2018-10-26 15:37 ` Josh Poimboeuf
2018-10-29 9:28 ` Mark Rutland
2018-10-29 9:28 ` Mark Rutland
2018-10-29 15:42 ` Josh Poimboeuf
2018-10-29 15:42 ` Josh Poimboeuf
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=20181031185800.6aa17c91@blackhole \
--to=duwe@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.