From: yuanjunqing <yuanjunqing66@163.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: paulburton@kernel.org, chenhc@lemote.com,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
liulichao@loongson.cn
Subject: Re: [PATCH] MIPS: Fix IRQ tracing when call handle_fpe()
Date: Tue, 26 May 2020 15:07:16 +0800 [thread overview]
Message-ID: <76f2c756-0ae4-83f5-becf-6f1b3319f6fd@163.com> (raw)
In-Reply-To: <20200525084234.GA5057@alpha.franken.de>
在 2020/5/25 下午4:42, Thomas Bogendoerfer 写道:
> On Mon, May 25, 2020 at 11:31:23AM +0800, YuanJunQing wrote:
>> Register "a1" is unsaved in this function,
>> when CONFIG_TRACE_IRQFLAGS is enabled,
>> the TRACE_IRQS_OFF macro will call trace_hardirqs_off(),
>> and this may change register "a1".
>> The variment of register "a1" may send SIGFPE signal
>> to task when call do_fpe(),and this may kill the task.
>>
>> Signed-off-by: YuanJunQing <yuanjunqing66@163.com>
>> ---
>> arch/mips/kernel/genex.S | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/mips/kernel/genex.S b/arch/mips/kernel/genex.S
>> index 8236fb291e3f..956a76429773 100644
>> --- a/arch/mips/kernel/genex.S
>> +++ b/arch/mips/kernel/genex.S
>> @@ -480,16 +480,18 @@ NESTED(nmi_handler, PT_SIZE, sp)
>> /* gas fails to assemble cfc1 for some archs (octeon).*/ \
>> .set mips1
>> SET_HARDFLOAT
>> - cfc1 a1, fcr31
>> + cfc1 s0, fcr31
>> .set pop
>> CLI
>> TRACE_IRQS_OFF
>> + move a1,s0
>> .endm
> do we realy need to read fcr31 that early ? Wouldn't it work to
> just move the cfc1 below TRACE_IRQS_OFF ?
>
> Thomas.
yes, it can work when we just move the cfc1 below TRACE_IRQS_OFF,
and the code is written as follows.
CLI
TRACE_IRQS_OFF
.set mips1
SET_HARDFLOAT
cfc1 a1, fcr31
.set pop
.endm
next prev parent reply other threads:[~2020-05-26 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 3:31 YuanJunQing
2020-05-25 8:34 ` Sergei Shtylyov
2020-05-25 8:42 ` Thomas Bogendoerfer
2020-05-26 7:07 ` yuanjunqing [this message]
2020-05-26 13:04 ` Thomas Bogendoerfer
2020-05-27 2:31 ` yuanjunqing
2020-05-26 13:05 ` Thomas Bogendoerfer
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=76f2c756-0ae4-83f5-becf-6f1b3319f6fd@163.com \
--to=yuanjunqing66@163.com \
--cc=chenhc@lemote.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liulichao@loongson.cn \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®