Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carsten Langgaard <carstenl@mips.com>
To: sgi-mips <linux@cthulhu.engr.sgi.com>
Subject: Re: Exceptions
Date: Thu, 09 Dec 1999 09:05:47 +0100	[thread overview]
Message-ID: <384F62DB.8DE09E3B@mips.com> (raw)
In-Reply-To: 384EDFC5.FFAE939A@ti.com

Jeff Harrell wrote:

> I have been working through the initialization code for the MIPS/Linux
> kernel and have traced through to the point
> where the MIPS exceptions are installed.  I have not been able to locate
> the following routines
>
>         handle_adel
>         handle_ades
>         handle_sys
>         handle_bp
>         handle_n
>         handle_cpu
>         handle_ov
>         handle_tr
>         handle_fpe
>
> I see where these are defined by "extern asmlinkage" references but
> can't locate the actual implementation of these
> exceptions.  Any idea what files these routines might be located in?
> Any help would be greatly appreciated

They are located in arch/mips/kernel/entry.S
They are a little hard to find as they use the BUILD_HANDLER macro to
extract the routines.

>
>
> Thank you,
> Jeff Harrell
>
> ---------8< excerpt from kernel/traps.c -----
>
>  set_except_vector(1, handle_mod);
>  set_except_vector(2, handle_tlbl);
>  set_except_vector(3, handle_tlbs);
>  set_except_vector(4, handle_adel);
>  set_except_vector(5, handle_ades);
>  /*
>   * The Data Bus Error/ Instruction Bus Errors are signaled
>   * by external hardware.  Therefore these two expection have
>   * board specific handlers.
>   */
>  set_except_vector(6, handle_ibe);
>  set_except_vector(7, handle_dbe);
>  ibe_board_handler = default_be_board_handler;
>  dbe_board_handler = default_be_board_handler;
>
>  set_except_vector(8, handle_sys);
>  set_except_vector(9, handle_bp);
>  set_except_vector(10, handle_ri);
>  set_except_vector(11, handle_cpu);
>  set_except_vector(12, handle_ov);
>  set_except_vector(13, handle_tr);
>  set_except_vector(15, handle_fpe);
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Jeff Harrell                    Work:  (801) 619-6104
> Broadband Access group/TI
> jharrell@ti.com
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--
_    _ ____  ___   Carsten Langgaard   mailto:carstenl@mips.com
|\  /|||___)(___   MIPS Denmark        Direct: +45 4486 5527
| \/ |||    ____)  Lautrupvang 2B      Switch: +45 4486 5555
TECHNOLOGIES INC   2750 Ballerup       Fax...: +45 4486 5556
                   Denmark               http://www.mips.com

  reply	other threads:[~1999-12-09  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-08 22:46 Exceptions Jeff Harrell
1999-12-09  8:05 ` Carsten Langgaard [this message]
1999-12-09 10:44   ` Exceptions 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=384F62DB.8DE09E3B@mips.com \
    --to=carstenl@mips.com \
    --cc=linux@cthulhu.engr.sgi.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