linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: WANG Xuerui <kernel@xen0n.name>
To: yuanjunqing <yuanjunqing66@163.com>, tsbogend@alpha.franken.de
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	liulichao@loongson.cn
Subject: Re: [PATCH] function:stacktrace/mips: Fix function:stacktrace for mips
Date: Fri, 29 May 2020 17:41:31 +0800	[thread overview]
Message-ID: <43f35844-f78a-74a2-0e3d-184c3567d74f@xen0n.name> (raw)
In-Reply-To: <11c90f15-0a25-e628-c8db-53343c351085@163.com>

On 2020/5/29 17:29, yuanjunqing wrote:

> May I ask if you have received this email.

At least I have received the complete thread in my inbox, so others may 
well have no problem.

It's not polite to ping maintainers just one day after sending your 
patch BTW; keep the patch submitting guide[1] under your pillow.

Lastly, don't top-post even though your message body is short.


[1]: 
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#don-t-get-discouraged-or-impatient


And a bit of review while we're at it...

>
> 在 2020/5/28 下午8:36, YuanJunQing 写道:
>> ftrace_call as global symbol in ftrace_caller(), this
>> will cause function:stacktrace can not work well.
Chinglish. I can't understand this despite being a Chinese myself...
>> i.e. echo do_IRQ:stacktrace > set_ftrace_filte
The commit message is truncated? I can't seem to make sense of this line.
>>
>> Signed-off-by: YuanJunQing <yuanjunqing66@163.com>
>> ---
>>   arch/mips/kernel/mcount.S | 13 +++++++++++--
>>   1 file changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/mips/kernel/mcount.S b/arch/mips/kernel/mcount.S
>> index cff52b283e03..cd5545764e5f 100644
>> --- a/arch/mips/kernel/mcount.S
>> +++ b/arch/mips/kernel/mcount.S
>> @@ -87,8 +87,15 @@ EXPORT_SYMBOL(_mcount)
>>   	PTR_LA   t1, _etext
>>   	sltu     t3, t1, a0	/* t3 = (a0 > _etext) */
>>   	or       t1, t2, t3
>> +	PTR_LA	 t2, stlab-4 	/* t2: "function:stacktrace" return address */
>> +	move	 a1, AT		/* arg2: parent's return address */
>>   	beqz     t1, ftrace_call
>> -	 nop
>> +	 nop			/* "function:stacktrace" return address */
>> +stlab:
>> +	PTR_LA	t2, stlab-4
>> +	/* ftrace_call_end: ftrace_call return address */
>> +	beq	t2,ra, ftrace_call_end
>> +	nop
>>   #if defined(KBUILD_MCOUNT_RA_ADDRESS) && defined(CONFIG_32BIT)
>>   	PTR_SUBU a0, a0, 16	/* arg1: adjust to module's recorded callsite */
>>   #else
>> @@ -98,7 +105,9 @@ EXPORT_SYMBOL(_mcount)
>>   	.globl ftrace_call
>>   ftrace_call:
>>   	nop	/* a placeholder for the call to a real tracing function */
>> -	 move	a1, AT		/* arg2: parent's return address */
>> +	move	ra, t2		/* t2: "function:stacktrace" return address */
>> +
>> +ftrace_call_end:
>>   
>>   #ifdef CONFIG_FUNCTION_GRAPH_TRACER
>>   	.globl ftrace_graph_call

  reply	other threads:[~2020-05-29  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 12:36 [PATCH] function:stacktrace/mips: Fix function:stacktrace for mips YuanJunQing
2020-05-29  9:29 ` yuanjunqing
2020-05-29  9:41   ` WANG Xuerui [this message]
2020-06-04  1:17     ` Maciej W. Rozycki
2020-06-04  3:25       ` yuanjunqing

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=43f35844-f78a-74a2-0e3d-184c3567d74f@xen0n.name \
    --to=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=liulichao@loongson.cn \
    --cc=tsbogend@alpha.franken.de \
    --cc=yuanjunqing66@163.com \
    /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).