Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: Florian DELIZY <florian.delizy@sagem.com>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: Réf. : does the linux kernel use k0, k1 regs?
Date: Mon, 16 Jan 2006 13:26:56 +0100	[thread overview]
Message-ID: <43CB9110.7040003@mips.com> (raw)
In-Reply-To: <50c9a2250601160401ifa8337cs2f8638f0077f37ed@mail.gmail.com>

zhuzhenhua wrote:
> thanks for all
> now in my NMI interrupt, i first move k0 value to Desave, then use k0 to
> handle, and then eret.
> it can work.

It can work as long as you understand that you can't use
EJTAG breakpoints or (more difficult to avoid) handle DINT
events that happen during your NMI handler.

		Regards,

		Kevin K.

      reply	other threads:[~2006-01-16 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  7:24 Réf. : does the linux kernel use k0, k1 regs? Florian DELIZY
2006-01-16 12:01 ` zhuzhenhua
2006-01-16 12:26   ` Kevin D. Kissell [this message]

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=43CB9110.7040003@mips.com \
    --to=kevink@mips.com \
    --cc=florian.delizy@sagem.com \
    --cc=linux-mips@linux-mips.org \
    --cc=zzh.hust@gmail.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