From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> To: Michael Ellerman <mpe@ellerman.id.au>, Steven Rostedt <rostedt@goodmis.org>, Masami Hiramatsu <mhiramat@kernel.org>, Ingo Molnar <mingo@kernel.org>, Nicholas Piggin <npiggin@gmail.com> Cc: <linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org> Subject: [PATCH 0/7] powerpc/ftrace: Patch out -mprofile-kernel instructions Date: Tue, 18 Jun 2019 20:16:59 +0530 [thread overview] Message-ID: <cover.1560868106.git.naveen.n.rao@linux.vnet.ibm.com> (raw) Changes since RFC: - Patches 1 and 2: No changes - Patch 3: rename function to ftrace_replace_code_rec() to signify that it acts on a ftrace record. - Patch 4: numerous small changes, including those suggested by Nick Piggin. - Patch 4: additionally handle scenario where __ftrace_make_call() can be invoked without having called __ftrace_make_call_prep(), when a kernel module is loaded while function tracing is active. - Patch 5 to 7: new, to have ftrace claim ownership of two instructions, and to have kprobes work properly with this. -- On powerpc64, -mprofile-kernel results in two instructions being emitted: 'mflr r0' and 'bl _mcount'. So far, we were only nop'ing out the branch to _mcount(). This series implements an approach to also nop out the preceding mflr. - Naveen Naveen N. Rao (7): ftrace: Expose flags used for ftrace_replace_code() x86/ftrace: Fix use of flags in ftrace_replace_code() ftrace: Expose __ftrace_replace_code() powerpc/ftrace: Additionally nop out the preceding mflr with -mprofile-kernel powerpc/ftrace: Update ftrace_location() for powerpc -mprofile-kernel kprobes/ftrace: Use ftrace_location() when [dis]arming probes powerpc/kprobes: Allow probing on any ftrace address arch/powerpc/kernel/kprobes-ftrace.c | 30 +++ arch/powerpc/kernel/trace/ftrace.c | 272 ++++++++++++++++++++++++--- arch/x86/kernel/ftrace.c | 3 +- include/linux/ftrace.h | 7 + kernel/kprobes.c | 10 +- kernel/trace/ftrace.c | 17 +- 6 files changed, 300 insertions(+), 39 deletions(-) -- 2.22.0
WARNING: multiple messages have this Message-ID (diff)
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> To: Michael Ellerman <mpe@ellerman.id.au>, Steven Rostedt <rostedt@goodmis.org>, Masami Hiramatsu <mhiramat@kernel.org>, Ingo Molnar <mingo@kernel.org>, Nicholas Piggin <npiggin@gmail.com> Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/7] powerpc/ftrace: Patch out -mprofile-kernel instructions Date: Tue, 18 Jun 2019 20:16:59 +0530 [thread overview] Message-ID: <cover.1560868106.git.naveen.n.rao@linux.vnet.ibm.com> (raw) Changes since RFC: - Patches 1 and 2: No changes - Patch 3: rename function to ftrace_replace_code_rec() to signify that it acts on a ftrace record. - Patch 4: numerous small changes, including those suggested by Nick Piggin. - Patch 4: additionally handle scenario where __ftrace_make_call() can be invoked without having called __ftrace_make_call_prep(), when a kernel module is loaded while function tracing is active. - Patch 5 to 7: new, to have ftrace claim ownership of two instructions, and to have kprobes work properly with this. -- On powerpc64, -mprofile-kernel results in two instructions being emitted: 'mflr r0' and 'bl _mcount'. So far, we were only nop'ing out the branch to _mcount(). This series implements an approach to also nop out the preceding mflr. - Naveen Naveen N. Rao (7): ftrace: Expose flags used for ftrace_replace_code() x86/ftrace: Fix use of flags in ftrace_replace_code() ftrace: Expose __ftrace_replace_code() powerpc/ftrace: Additionally nop out the preceding mflr with -mprofile-kernel powerpc/ftrace: Update ftrace_location() for powerpc -mprofile-kernel kprobes/ftrace: Use ftrace_location() when [dis]arming probes powerpc/kprobes: Allow probing on any ftrace address arch/powerpc/kernel/kprobes-ftrace.c | 30 +++ arch/powerpc/kernel/trace/ftrace.c | 272 ++++++++++++++++++++++++--- arch/x86/kernel/ftrace.c | 3 +- include/linux/ftrace.h | 7 + kernel/kprobes.c | 10 +- kernel/trace/ftrace.c | 17 +- 6 files changed, 300 insertions(+), 39 deletions(-) -- 2.22.0
next reply other threads:[~2019-06-18 14:48 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-18 14:46 Naveen N. Rao [this message] 2019-06-18 14:46 ` [PATCH 0/7] powerpc/ftrace: Patch out -mprofile-kernel instructions Naveen N. Rao 2019-06-18 14:47 ` [PATCH 1/7] ftrace: Expose flags used for ftrace_replace_code() Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-18 14:47 ` [PATCH 2/7] x86/ftrace: Fix use of flags in ftrace_replace_code() Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-18 14:47 ` [PATCH 3/7] ftrace: Expose __ftrace_replace_code() Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-18 14:47 ` [PATCH 4/7] powerpc/ftrace: Additionally nop out the preceding mflr with -mprofile-kernel Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-19 5:14 ` Michael Ellerman 2019-06-19 7:10 ` Nicholas Piggin 2019-06-19 7:10 ` Nicholas Piggin 2019-06-19 9:53 ` Naveen N. Rao 2019-06-19 9:53 ` Naveen N. Rao 2019-06-19 10:41 ` Nicholas Piggin 2019-06-19 10:41 ` Nicholas Piggin 2019-06-19 17:14 ` Naveen N. Rao 2019-06-19 17:14 ` Naveen N. Rao 2019-06-18 14:47 ` [PATCH 5/7] powerpc/ftrace: Update ftrace_location() for powerpc -mprofile-kernel Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-18 15:45 ` Steven Rostedt 2019-06-18 15:45 ` Steven Rostedt 2019-06-18 18:11 ` Naveen N. Rao 2019-06-18 18:11 ` Naveen N. Rao 2019-06-18 18:23 ` Naveen N. Rao 2019-06-18 18:23 ` Naveen N. Rao 2019-06-18 18:32 ` Steven Rostedt 2019-06-18 18:32 ` Steven Rostedt 2019-06-19 7:56 ` Naveen N. Rao 2019-06-19 7:56 ` Naveen N. Rao 2019-06-19 9:28 ` Steven Rostedt 2019-06-19 9:28 ` Steven Rostedt 2019-06-18 14:47 ` [PATCH 6/7] kprobes/ftrace: Use ftrace_location() when [dis]arming probes Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-21 14:41 ` Masami Hiramatsu 2019-06-21 14:41 ` Masami Hiramatsu 2019-06-18 14:47 ` [PATCH 7/7] powerpc/kprobes: Allow probing on any ftrace address Naveen N. Rao 2019-06-18 14:47 ` Naveen N. Rao 2019-06-21 14:50 ` Masami Hiramatsu 2019-06-21 14:50 ` Masami Hiramatsu 2019-06-22 3:49 ` Joe Perches 2019-06-22 3:49 ` Joe Perches 2019-06-26 9:39 ` Naveen N. Rao 2019-06-26 9:39 ` Naveen N. Rao
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=cover.1560868106.git.naveen.n.rao@linux.vnet.ibm.com \ --to=naveen.n.rao@linux.vnet.ibm.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mhiramat@kernel.org \ --cc=mingo@kernel.org \ --cc=mpe@ellerman.id.au \ --cc=npiggin@gmail.com \ --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: linkBe 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.