From: Chris Dearman <chris@mips.com>
To: linux-mips <linux-mips@linux-mips.org>
Subject: [PATCH] Avoid potential hazard on Context register
Date: Sat, 10 Oct 2009 23:07:21 -0700 [thread overview]
Message-ID: <4AD17619.1000201@mips.com> (raw)
set_saved_sp reads Context register. Avoid reading stale value from
earlier incomplete write
Signed-off-by: Chris Dearman <chris@mips.com>
---
arch/mips/kernel/head.S | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/mips/kernel/head.S b/arch/mips/kernel/head.S
index 531ce7b..ea695d9 100644
--- a/arch/mips/kernel/head.S
+++ b/arch/mips/kernel/head.S
@@ -191,6 +191,7 @@ NESTED(kernel_entry, 16, sp) # kernel entry point
/* Set the SP after an empty pt_regs. */
PTR_LI sp, _THREAD_SIZE - 32 - PT_SIZE
PTR_ADDU sp, $28
+ back_to_back_c0_hazard
set_saved_sp sp, t0, t1
PTR_SUBU sp, 4 * SZREG # init stack pointer
next reply other threads:[~2009-10-11 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 6:07 Chris Dearman [this message]
2009-10-11 13:39 ` [PATCH] Avoid potential hazard on Context register Ralf Baechle
2009-10-11 14:53 ` Ralf Baechle
2009-10-11 20:26 ` Chris Dearman
2009-10-12 3:20 ` Ralf Baechle
2009-10-11 20:05 ` Chris Dearman
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=4AD17619.1000201@mips.com \
--to=chris@mips.com \
--cc=linux-mips@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;
as well as URLs for NNTP newsgroup(s).