From: Ralf Baechle <ralf@linux-mips.org>
To: Chris Dearman <chris@mips.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] Avoid potential hazard on Context register
Date: Sun, 11 Oct 2009 15:39:12 +0200 [thread overview]
Message-ID: <20091011133912.GA15684@linux-mips.org> (raw)
In-Reply-To: <4AD17619.1000201@mips.com>
On Sat, Oct 10, 2009 at 11:07:21PM -0700, Chris Dearman wrote:
> set_saved_sp reads Context register. Avoid reading stale value from
> earlier incomplete write
Which is executed fairly frequently. So it'll be cheaper to fix the issue
in the writers. Will post patch in a few minutes.
I'm curious, did you actually manage to trigger this one? The time between
the instructions should be fairly long but then again the 34K has been
good for a few surprises!
Ralf
next prev parent reply other threads:[~2009-10-11 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 6:07 [PATCH] Avoid potential hazard on Context register Chris Dearman
2009-10-11 13:39 ` Ralf Baechle [this message]
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=20091011133912.GA15684@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=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).