linux-mips
[Top] [All Lists]

Re: MIPS: return after handling coprocessor 2 exception

To: David Daney <ddaney@caviumnetworks.com>
Subject: Re: MIPS: return after handling coprocessor 2 exception
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
Date: Fri, 18 Jun 2010 11:54:38 +0400
Cc: Jesper Nilsson <jesper@jni.nu>, Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
In-reply-to: <4C1A57AE.9080706@caviumnetworks.com>
Organization: NIISI RAN
References: <20100617132554.GB24162@jni.nu> <4C1A57AE.9080706@caviumnetworks.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
On 17.06.2010 21:13, David Daney wrote:
On 06/17/2010 06:25 AM, Jesper Nilsson wrote:
Breaking here dropped us to the default code which always sends
a SIGILL to the current process, no matter what the CU2 notifier says.

Signed-off-by: Jesper Nilsson<jesper@jni.nu>
[...]
case 2:
raw_notifier_call_chain(&cu2_chain, CU2_EXCEPTION, regs);
- break;
+ return;


What happens when the call chain is empty, and the proper action *is*
SIGILL?

It's never empty, in fact. The default notifier declared at top of traps.c sends SIGILL. The problem that current code is sending SIGILL in all cases.

Gleb.

<Prev in Thread] Current Thread [Next in Thread>