From: Michael Ellerman <mpe@ellerman•id.au>
To: Michael Ellerman <mpe@ellerman•id.au>, <linuxppc-dev@ozlabs•org>
Cc: pmladek@suse•com, jeyu@redhat•com, jikos@kernel•org,
linux-kernel@vger•kernel.org, rostedt@goodmis•org,
kamalesh@linux•vnet.ibm.com, duwe@lst•de,
live-patching@vger•kernel.org, mbenes@suse•cz
Subject: Re: [4/5] powerpc/livepatch: Add livepatch stack to struct thread_info
Date: Tue, 19 Apr 2016 20:16:32 +1000 (AEST) [thread overview]
Message-ID: <3qq1Bm5pBgz9t8m@ozlabs.org> (raw)
In-Reply-To: <1460552003-15409-5-git-send-email-mpe@ellerman.id.au>
On Wed, 2016-13-04 at 12:53:22 UTC, Michael Ellerman wrote:
> In order to support live patching we need to maintain an alternate
> stack of TOC & LR values. We use the base of the stack for this, and
> store the "live patch stack pointer" in struct thread_info.
>
> Unlike the other fields of thread_info, we can not statically initialise
> that value, so it must be done at run time.
>
> This patch just adds the code to support that, it is not enabled until
> the next patch which actually adds live patch support.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman•id.au>
> Acked-by: Balbir Singh <bsingharora@gmail•com>
Applied to powerpc next.
https://git.kernel.org/powerpc/c/5d31a96e6c0187f2c5d7004e00
cheers
next prev parent reply other threads:[~2016-04-19 10:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:53 [PATCH 0/5] Live patching for powerpc Michael Ellerman
2016-04-13 12:53 ` [PATCH 1/5] ftrace: Make ftrace_location_range() global Michael Ellerman
2016-04-19 10:16 ` [1/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 2/5] livepatch: Allow architectures to specify an alternate ftrace location Michael Ellerman
2016-04-14 12:01 ` Miroslav Benes
2016-04-14 13:06 ` Michael Ellerman
2016-04-14 14:06 ` Miroslav Benes
2016-04-19 10:16 ` [2/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 3/5] powerpc/livepatch: Add livepatch header Michael Ellerman
2016-04-14 12:18 ` Miroslav Benes
2016-04-14 12:23 ` Miroslav Benes
2016-04-14 13:12 ` Michael Ellerman
2016-04-19 10:16 ` [3/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 4/5] powerpc/livepatch: Add livepatch stack to struct thread_info Michael Ellerman
2016-04-19 10:16 ` Michael Ellerman [this message]
2016-04-13 12:53 ` [PATCH 5/5] powerpc/livepatch: Add live patching support on ppc64le Michael Ellerman
2016-04-19 10:16 ` [5/5] " Michael Ellerman
2016-04-13 13:01 ` [PATCH 0/5] Live patching for powerpc Miroslav Benes
2016-04-13 13:22 ` Jiri Kosina
2016-04-14 6:49 ` Michael Ellerman
2016-04-14 12:57 ` Torsten Duwe
2016-04-14 13:08 ` Michael Ellerman
2016-04-14 15:20 ` Torsten Duwe
2016-04-14 16:41 ` Josh Poimboeuf
2016-04-15 11:22 ` Michael Ellerman
2016-04-15 12:59 ` Josh Poimboeuf
2016-04-15 13:21 ` Michael Ellerman
2016-04-14 14:34 ` Jiri Kosina
2016-04-15 12:24 ` Michael Ellerman
2016-04-15 15:07 ` Jiri Kosina
2016-04-19 21:42 ` Balbir Singh
2016-04-19 21:52 ` Jiri Kosina
2016-04-13 18:22 ` Jessica Yu
2016-04-14 13:28 ` Miroslav Benes
2016-04-14 19:20 ` Jessica Yu
2016-04-15 8:28 ` Miroslav Benes
2016-04-15 10:01 ` 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=3qq1Bm5pBgz9t8m@ozlabs.org \
--to=mpe@ellerman$(echo .)id.au \
--cc=duwe@lst$(echo .)de \
--cc=jeyu@redhat$(echo .)com \
--cc=jikos@kernel$(echo .)org \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=live-patching@vger$(echo .)kernel.org \
--cc=mbenes@suse$(echo .)cz \
--cc=pmladek@suse$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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