From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Naveen N Rao <naveen@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 00/17] powerpc/ftrace: refactor and add support for -fpatchable-function-entry
Date: Wed, 23 Aug 2023 21:55:55 +1000 [thread overview]
Message-ID: <169279175579.797584.3091771580602329496.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <cover.1687166935.git.naveen@kernel.org>
On Mon, 19 Jun 2023 15:17:18 +0530, Naveen N Rao wrote:
> Since RFC (*):
> - Patches 1 and 17 have been included in this series due to
> dependencies. Both had been posted out separately.
> - Patch 10 has a small change to not throw errors when checking
> instruction sequence generated by older toolchains.
>
> This has had more testing since and this looks good to me. Christophe
> mentioned that this results in a slowdown with ftrace [de-]activation on
> ppc32, but that isn't performance critical and we can address that
> separately.
>
> [...]
Patch 1-16 applied to powerpc/next.
[01/17] powerpc/ftrace: Fix dropping weak symbols with older toolchains
https://git.kernel.org/powerpc/c/f6834c8c59a8e977a6f6e4f96c5d28dfa5db8430
[02/17] powerpc/module: Remove unused .ftrace.tramp section
https://git.kernel.org/powerpc/c/0240605931ec300ddb698020edff05a4c93edbb2
[03/17] powerpc64/ftrace: Move ELFv1 and -pg support code into a separate file
https://git.kernel.org/powerpc/c/7f7797b372693ce17223678428490dea2b3e4389
[04/17] powerpc/ftrace: Simplify function_graph support in ftrace.c
https://git.kernel.org/powerpc/c/96d7a13610abcf6bff9d0d0e195c6d2650310125
[05/17] powerpc/ftrace: Use FTRACE_REGS_ADDR to identify the correct ftrace trampoline
https://git.kernel.org/powerpc/c/b5efb61c70f8ba9b1e168185530b9c7342184a4c
[06/17] powerpc/ftrace: Extend ftrace support for large kernels to ppc32
https://git.kernel.org/powerpc/c/f3993a0330e2d11e42c095810c6c33084024df46
[07/17] powerpc/ftrace: Consolidate ftrace support into fewer files
https://git.kernel.org/powerpc/c/bad90aa52d9a0141c41e00ccd4c40be30a29acc6
[08/17] powerpc/ftrace: Refactor ftrace_modify_code()
https://git.kernel.org/powerpc/c/f4fcbf2e093e25a7faa8a3c2a5097524114e9547
[09/17] powerpc/ftrace: Stop re-purposing linker generated long branches for ftrace
https://git.kernel.org/powerpc/c/33bb8a0be9c826fce545ae390ecaf91e96b5db43
[10/17] powerpc/ftrace: Add separate ftrace_init_nop() with additional validation
https://git.kernel.org/powerpc/c/cc93b9233230312a8a905fabd590c405d60f9edd
[11/17] powerpc/ftrace: Simplify ftrace_make_nop()
https://git.kernel.org/powerpc/c/562bde0bfc968d212d10ba6bf921a0774feebbac
[12/17] powerpc/ftrace: Simplify ftrace_make_call()
https://git.kernel.org/powerpc/c/9365e23b15f28b7b3b333a7fc6f4c8e9464ca99f
[13/17] powerpc/ftrace: Simplify ftrace_modify_call()
https://git.kernel.org/powerpc/c/67385738e3c248673668663ffb434ae4e0abf7f1
[14/17] powerpc/ftrace: Replace use of ftrace_call_replace() with ftrace_create_branch_inst()
https://git.kernel.org/powerpc/c/a26ce4272eea2b20d4f39b9d7e56daf0c77151d8
[15/17] powerpc/ftrace: Implement ftrace_replace_code()
https://git.kernel.org/powerpc/c/c91c5a828685563c24ab8879d8386de356d9085a
[16/17] powerpc/ftrace: Add support for -fpatchable-function-entry
https://git.kernel.org/powerpc/c/0f71dcfb4aef6043da6cc509e7a7f6a3ae87c12d
cheers
prev parent reply other threads:[~2023-08-23 12:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:47 [PATCH 00/17] powerpc/ftrace: refactor and add support for -fpatchable-function-entry Naveen N Rao
2023-06-19 9:47 ` [PATCH 01/17] powerpc/ftrace: Fix dropping weak symbols with older toolchains Naveen N Rao
2023-06-23 5:10 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 02/17] powerpc/module: Remove unused .ftrace.tramp section Naveen N Rao
2023-06-23 5:12 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 03/17] powerpc64/ftrace: Move ELFv1 and -pg support code into a separate file Naveen N Rao
2023-06-23 5:13 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 04/17] powerpc/ftrace: Simplify function_graph support in ftrace.c Naveen N Rao
2023-06-23 5:14 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 05/17] powerpc/ftrace: Use FTRACE_REGS_ADDR to identify the correct ftrace trampoline Naveen N Rao
2023-06-23 5:15 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 06/17] powerpc/ftrace: Extend ftrace support for large kernels to ppc32 Naveen N Rao
2023-06-23 5:21 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 07/17] powerpc/ftrace: Consolidate ftrace support into fewer files Naveen N Rao
2023-06-23 5:25 ` Christophe Leroy
2023-06-28 7:32 ` Naveen N Rao
2023-06-19 9:47 ` [PATCH 08/17] powerpc/ftrace: Refactor ftrace_modify_code() Naveen N Rao
2023-06-23 5:27 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 09/17] powerpc/ftrace: Stop re-purposing linker generated long branches for ftrace Naveen N Rao
2023-06-23 5:28 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 10/17] powerpc/ftrace: Add separate ftrace_init_nop() with additional validation Naveen N Rao
2023-06-23 5:29 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 11/17] powerpc/ftrace: Simplify ftrace_make_nop() Naveen N Rao
2023-06-23 5:30 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 12/17] powerpc/ftrace: Simplify ftrace_make_call() Naveen N Rao
2023-06-23 5:30 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 13/17] powerpc/ftrace: Simplify ftrace_modify_call() Naveen N Rao
2023-06-23 5:31 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 14/17] powerpc/ftrace: Replace use of ftrace_call_replace() with ftrace_create_branch_inst() Naveen N Rao
2023-06-23 5:32 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 15/17] powerpc/ftrace: Implement ftrace_replace_code() Naveen N Rao
2023-06-23 5:32 ` Christophe Leroy
2023-06-19 9:47 ` [PATCH 16/17] powerpc/ftrace: Add support for -fpatchable-function-entry Naveen N Rao
2023-06-23 5:37 ` Christophe Leroy
2023-06-28 7:40 ` Naveen N Rao
2023-06-19 9:47 ` [PATCH 17/17] powerpc/ftrace: Create a dummy stackframe to fix stack unwind Naveen N Rao
2023-06-23 5:40 ` Christophe Leroy
2023-06-28 7:43 ` Naveen N Rao
2023-08-23 11:55 ` Michael Ellerman [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=169279175579.797584.3091771580602329496.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen@kernel.org \
--cc=rostedt@goodmis.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.