From: Christophe Leroy <christophe.leroy@csgroup.eu> To: Josh Poimboeuf <jpoimboe@redhat.com>, Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>, Joe Lawrence <joe.lawrence@redhat.com>, Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>, "Naveen N . Rao" <naveen.n.rao@linux.vnet.ibm.com> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, live-patching@vger.kernel.org Subject: [PATCH v1 0/5] Implement livepatch on PPC32 Date: Thu, 28 Oct 2021 14:24:00 +0200 [thread overview] Message-ID: <cover.1635423081.git.christophe.leroy@csgroup.eu> (raw) This series implements livepatch on PPC32. This is largely copied from what's done on PPC64. Christophe Leroy (5): livepatch: Fix build failure on 32 bits processors powerpc/ftrace: No need to read LR from stack in _mcount() powerpc/ftrace: Add module_trampoline_target() for PPC32 powerpc/ftrace: Activate HAVE_DYNAMIC_FTRACE_WITH_REGS on PPC32 powerpc/ftrace: Add support for livepatch to PPC32 arch/powerpc/Kconfig | 2 +- arch/powerpc/include/asm/livepatch.h | 4 +- arch/powerpc/kernel/module_32.c | 33 +++++ arch/powerpc/kernel/trace/ftrace.c | 53 +++----- arch/powerpc/kernel/trace/ftrace_32.S | 187 ++++++++++++++++++++++++-- kernel/livepatch/core.c | 4 +- 6 files changed, 230 insertions(+), 53 deletions(-) -- 2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Christophe Leroy <christophe.leroy@csgroup.eu> To: Josh Poimboeuf <jpoimboe@redhat.com>, Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>, Joe Lawrence <joe.lawrence@redhat.com>, Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>, "Naveen N . Rao" <naveen.n.rao@linux.vnet.ibm.com> Cc: live-patching@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: [PATCH v1 0/5] Implement livepatch on PPC32 Date: Thu, 28 Oct 2021 14:24:00 +0200 [thread overview] Message-ID: <cover.1635423081.git.christophe.leroy@csgroup.eu> (raw) This series implements livepatch on PPC32. This is largely copied from what's done on PPC64. Christophe Leroy (5): livepatch: Fix build failure on 32 bits processors powerpc/ftrace: No need to read LR from stack in _mcount() powerpc/ftrace: Add module_trampoline_target() for PPC32 powerpc/ftrace: Activate HAVE_DYNAMIC_FTRACE_WITH_REGS on PPC32 powerpc/ftrace: Add support for livepatch to PPC32 arch/powerpc/Kconfig | 2 +- arch/powerpc/include/asm/livepatch.h | 4 +- arch/powerpc/kernel/module_32.c | 33 +++++ arch/powerpc/kernel/trace/ftrace.c | 53 +++----- arch/powerpc/kernel/trace/ftrace_32.S | 187 ++++++++++++++++++++++++-- kernel/livepatch/core.c | 4 +- 6 files changed, 230 insertions(+), 53 deletions(-) -- 2.31.1
next reply other threads:[~2021-10-28 12:24 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-28 12:24 Christophe Leroy [this message] 2021-10-28 12:24 ` [PATCH v1 0/5] Implement livepatch on PPC32 Christophe Leroy 2021-10-28 12:24 ` [PATCH v1 1/5] livepatch: Fix build failure on 32 bits processors Christophe Leroy 2021-10-28 12:24 ` Christophe Leroy 2021-11-08 9:47 ` Petr Mladek 2021-11-08 9:47 ` Petr Mladek 2021-10-28 12:24 ` [PATCH v1 2/5] powerpc/ftrace: No need to read LR from stack in _mcount() Christophe Leroy 2021-10-28 12:24 ` Christophe Leroy 2021-10-28 12:24 ` [PATCH v1 3/5] powerpc/ftrace: Add module_trampoline_target() for PPC32 Christophe Leroy 2021-10-28 12:24 ` Christophe Leroy 2021-10-28 12:24 ` [PATCH v1 4/5] powerpc/ftrace: Activate HAVE_DYNAMIC_FTRACE_WITH_REGS on PPC32 Christophe Leroy 2021-10-28 12:24 ` Christophe Leroy 2021-10-28 12:24 ` [PATCH v1 5/5] powerpc/ftrace: Add support for livepatch to PPC32 Christophe Leroy 2021-10-28 12:24 ` Christophe Leroy 2021-11-08 10:01 ` Petr Mladek 2021-11-08 10:01 ` Petr Mladek 2021-10-28 13:35 ` [PATCH v1 0/5] Implement livepatch on PPC32 Steven Rostedt 2021-10-28 13:35 ` Steven Rostedt 2021-12-13 14:39 ` Christophe Leroy 2021-12-13 14:39 ` Christophe Leroy 2021-12-13 17:15 ` Steven Rostedt 2021-12-13 17:15 ` Steven Rostedt 2021-12-13 17:30 ` Christophe Leroy 2021-12-13 17:30 ` Christophe Leroy 2021-12-13 17:33 ` Steven Rostedt 2021-12-13 17:33 ` Steven Rostedt 2021-12-13 17:50 ` Christophe Leroy 2021-12-13 17:50 ` Christophe Leroy 2021-12-13 18:54 ` Steven Rostedt 2021-12-13 18:54 ` Steven Rostedt 2021-12-13 19:33 ` Christophe Leroy 2021-12-13 19:33 ` Christophe Leroy 2021-12-13 19:46 ` Steven Rostedt 2021-12-13 19:46 ` Steven Rostedt 2021-12-14 6:09 ` Christophe Leroy 2021-12-14 6:09 ` Christophe Leroy 2021-12-14 7:35 ` Christophe Leroy 2021-12-14 7:35 ` Christophe Leroy 2021-12-14 14:01 ` Steven Rostedt 2021-12-14 14:01 ` Steven Rostedt 2021-12-18 16:12 ` Christophe Leroy 2021-12-18 16:12 ` Christophe Leroy 2021-12-14 14:25 ` Heiko Carstens 2021-12-14 14:25 ` Heiko Carstens 2021-12-14 15:12 ` Christophe Leroy 2021-12-14 15:12 ` Christophe Leroy 2021-11-01 14:50 ` Miroslav Benes 2021-11-01 14:50 ` Miroslav Benes 2021-11-24 22:34 ` Michael Ellerman 2021-11-25 5:49 ` Christophe Leroy 2021-12-07 13:26 ` Michael Ellerman 2021-12-07 13:26 ` Michael Ellerman
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.1635423081.git.christophe.leroy@csgroup.eu \ --to=christophe.leroy@csgroup.eu \ --cc=jikos@kernel.org \ --cc=joe.lawrence@redhat.com \ --cc=jpoimboe@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=live-patching@vger.kernel.org \ --cc=mbenes@suse.cz \ --cc=mingo@redhat.com \ --cc=naveen.n.rao@linux.vnet.ibm.com \ --cc=pmladek@suse.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.