From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [v3][PATCH 2/3] ppc/kprobe: complete kprobe and migrate exception frame
Date: Wed, 12 Sep 2012 16:38:22 +0800 [thread overview]
Message-ID: <505049FE.8060204@windriver.com> (raw)
In-Reply-To: <1347342718.2603.38.camel@pasglop>
On 09/11/2012 01:51 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2012-09-11 at 10:20 +0800, Tiejun Chen wrote:
>> We can't emulate stwu since that may corrupt current exception stack.
>> So we will have to do real store operation in the exception return code.
>>
>> Firstly we'll allocate a trampoline exception frame below the kprobed
>> function stack and copy the current exception frame to the trampoline.
>> Then we can do this real store operation to implement 'stwu', and reroute
>> the trampoline frame to r1 to complete this exception migration.
>
> Ok, so not quite there yet :-)
>
> See below:
>
>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>> ---
>> arch/powerpc/kernel/entry_32.S | 45 ++++++++++++++++++++++++++++++++++------
>> arch/powerpc/kernel/entry_64.S | 32 ++++++++++++++++++++++++++++
>> 2 files changed, 71 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/entry_32.S b/arch/powerpc/kernel/entry_32.S
>> index ead5016..6cfe12f 100644
>> --- a/arch/powerpc/kernel/entry_32.S
>> +++ b/arch/powerpc/kernel/entry_32.S
>> @@ -831,19 +831,54 @@ restore_user:
>> bnel- load_dbcr0
>> #endif
>>
>> -#ifdef CONFIG_PREEMPT
>> b restore
>>
>> /* N.B. the only way to get here is from the beq following ret_from_except. */
>> resume_kernel:
>> + /* check current_thread_info, _TIF_EMULATE_STACK_STORE */
>> + CURRENT_THREAD_INFO(r9, r1)
>> + lwz r0,TI_FLAGS(r9)
>> + andis. r0,r0,_TIF_EMULATE_STACK_STORE@h
>> + beq+ 1f
>
> So you used r0 to load the TI_FLAGS and immediately clobbered it in
> andis. forcing you to re-load them later down. Instead, put them in r8
>
> lwz r8,TI_FLAGS(r9)
> andis. r0,r8,_TIF_*
> beq+ *
>
>> + addi r8,r1,INT_FRAME_SIZE /* Get the kprobed function entry */
>
> Then you put your entry in r8 ....
I'll update this for 32b and 64b sections.
>
>> + lwz r3,GPR1(r1)
>> + subi r3,r3,INT_FRAME_SIZE /* dst: Allocate a trampoline exception frame */
>> + mr r4,r1 /* src: current exception frame */
>> + li r5,INT_FRAME_SIZE /* size: INT_FRAME_SIZE */
>> + mr r1,r3 /* Reroute the trampoline frame to r1 */
>> + bl memcpy /* Copy from the original to the trampoline */
>
> Which you just clobbered... oops :-)
>
> So you need to store that old r1 somewhere fist then retrieve it
> after the memcpy call. That or open-code the memcpy to avoid all
> the clobbering problems.
Maybe we can use copy_and_flush() since looks copy_and_flush() only clobber r0,
r6 and LR explicitly.
I'll resync these comments for v4.
Tiejun
next prev parent reply other threads:[~2012-09-12 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 2:20 [v3][PATCH 1/3] powerpc/kprobe: introduce a new thread flag Tiejun Chen
2012-09-11 2:20 ` [v3][PATCH 2/3] ppc/kprobe: complete kprobe and migrate exception frame Tiejun Chen
2012-09-11 5:51 ` Benjamin Herrenschmidt
2012-09-12 8:38 ` tiejun.chen [this message]
2012-09-12 8:43 ` Benjamin Herrenschmidt
2012-09-12 8:55 ` tiejun.chen
2012-09-12 10:38 ` Benjamin Herrenschmidt
2012-09-13 10:36 ` tiejun.chen
2012-09-13 21:42 ` Benjamin Herrenschmidt
2012-09-11 2:20 ` [v3][PATCH 3/3] ppc/kprobe: don't emulate store when kprobe stwu r1 Tiejun Chen
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=505049FE.8060204@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).