From: Ralf Baechle <ralf@linux-mips.org>
To: Mikael Starvik <mikael.starvik@axis.com>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
David Daney <ddaney@caviumnetworks.com>
Subject: Re: COP2 unaligned -> SIGBUS
Date: Mon, 23 Nov 2009 11:56:19 +0000 [thread overview]
Message-ID: <20091123115619.GB4217@linux-mips.org> (raw)
In-Reply-To: <20091123113820.GA4217@linux-mips.org>
On Mon, Nov 23, 2009 at 11:38:20AM +0000, Ralf Baechle wrote:
> > Since there are now at least two users of cop2 I propose the following:
>
> Yes, the comment is not quite correct. CP2 has always been available for
> application specific extensions and a few imlementations have made use of
> that. I'll update the comment. Oh and the Praystation has a TLB.
On 2nd thought - there is one user of CU2 in the kernel - the Cavium support.
Nothing else in the stock Linux/MIPS kernel will ever enable c0_status.cu2,
so the attempt to execute a CP2 load or store instruction would result in a
Coprocessor Unusable exception which whould result in a SIGILL being
delivered to the offending process. On Cavium the instructions COP2 is
documented to not deliver any exceptions so there isn't really anything
that would need to be changed.
David - I think we should try to get rid of the processor specifics from
this core code so probably having notifiers to run on Address Error or
Coprocessor Unusable exceptions would be a solution? I also want to get
rid of the Cavium #ifdef from traps.c.
Ralf
next prev parent reply other threads:[~2009-11-23 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 6:31 COP2 unaligned -> SIGBUS Mikael Starvik
2009-11-23 11:38 ` Ralf Baechle
2009-11-23 11:56 ` Ralf Baechle [this message]
2009-11-24 18:17 ` Ralf Baechle
2009-11-24 18:40 ` SV: " Mikael Starvik
2009-11-24 22:12 ` Ralf Baechle
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=20091123115619.GB4217@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=mikael.starvik@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.