Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Sirotkin, Alexander" <demiurg@ti.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: do_ri
Date: Wed, 02 Jul 2003 18:36:01 +0300	[thread overview]
Message-ID: <3F02FBE1.7070107@ti.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1030702172634.21225B-100000@delta.ds2.pg.gda.pl>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Are you sure ?

Because "grep -r" shows only 

./arch/mips/kernel/traps.c:asmlinkage void do_ri(struct pt_regs *regs)
./arch/mips/kernel/traps.c:             do_ri(regs);
./arch/mips/lx/lxRi.c:  do_ri(regp);

On my linux-2.4.17_mvl21 kernel. And I'm quite sure that when my kernel 
crashes it's not being called from any of these places.

But then again, may be in may case it's getting called only because some

memory get overwritten.

Maciej W. Rozycki wrote:


On Wed, 2 Jul 2003, Sirotkin, Alexander wrote:



  

Can anyone please enlighten me about the do_ri function ? I could not

find any reference to what it does and when it's  called anywhere.

    



 It's called from arch/mips/kernel/entry.S or

arch/mips64/kernel/r4k_genex.S to handle the Reserved Instruction

exception. 



  


-- 

Alexander Sirotkin

SW Engineer



Texas Instruments

Broadband Communications Israel (BCIL)

Tel:  +972-9-9706587

________________________________________________________________________

"Those who do not understand Unix are condemned to reinvent it, poorly."

      -- Henry Spencer 

[-- Attachment #2: Type: text/html, Size: 1633 bytes --]

  reply	other threads:[~2003-07-02 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 15:16 do_ri Sirotkin, Alexander
2003-07-02 15:28 ` do_ri Maciej W. Rozycki
2003-07-02 15:36   ` Sirotkin, Alexander [this message]
2003-07-02 15:51     ` do_ri Geert Uytterhoeven
2003-07-02 15:57       ` do_ri Ralf Baechle
2003-07-02 16:08       ` do_ri Sirotkin, Alexander

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=3F02FBE1.7070107@ti.com \
    --to=demiurg@ti.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    /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