From: Thiemo Seufer <ths@networkno.de>
To: linux-mips@linux-mips.org
Cc: ralf@linux-mips.org
Subject: [PATCH] fix interrupt handling for R2 CPUs
Date: Mon, 15 May 2006 18:27:47 +0100 [thread overview]
Message-ID: <20060515172747.GF9026@networkno.de> (raw)
This patch ensures that
a) only the low bit is used for status flags if CONFIG_CPU_MIPSR2,
consistent with the use of di/ei.
b) the ERL/EXL bits get cleared as well.
Signed-off-by: Thiemo Seufer <ths@networkno.de>
--- linux-orig/include/asm-mips/interrupt.h 2006-04-24 12:02:35.000000000 +0100
+++ linux-work/include/asm-mips/interrupt.h 2006-05-15 18:10:49.000000000 +0100
@@ -102,6 +102,9 @@ __asm__ (
" mfc0 \\flags, $2, 1 \n"
#else
" mfc0 \\flags, $12 \n"
+#ifdef CONFIG_CPU_MIPSR2
+ " andi \\flags, 1 \n"
+#endif
#endif
" .set pop \n"
" .endm \n");
@@ -169,7 +172,7 @@ __asm__ (
* Fast, dangerous. Life is fun, life is good.
*/
" mfc0 $1, $12 \n"
- " ins $1, \\flags, 0, 1 \n"
+ " ins $1, \\flags, 0, 5 \n"
" mtc0 $1, $12 \n"
#else
" mfc0 $1, $12 \n"
next reply other threads:[~2006-05-15 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 17:27 Thiemo Seufer [this message]
2006-05-16 17:48 ` [PATCH] fix interrupt handling for R2 CPUs Ralf Baechle
2006-05-16 17:55 ` Thiemo Seufer
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=20060515172747.GF9026@networkno.de \
--to=ths@networkno.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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