From: Chris Dearman <chris@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] Avoid potential hazard on Context register
Date: Sun, 11 Oct 2009 13:05:52 -0700 [thread overview]
Message-ID: <4AD23AA0.9010702@mips.com> (raw)
In-Reply-To: <20091011133912.GA15684@linux-mips.org>
Ralf Baechle wrote:
> 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!
Yes... It actually showed up in 74k silicon at particular clock
frequencies. The dual issue pipeline does make it susceptible to these
"theoretical" problems ;)
Chris
--
Chris Dearman Desk: +1 408 530 5092 Cell: +1 650 224 8603
MIPS Technologies Inc 955 East Arques Ave, Sunnyvale CA 94085
prev parent reply other threads:[~2009-10-11 20:06 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
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 [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=4AD23AA0.9010702@mips.com \
--to=chris@mips.com \
--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;
as well as URLs for NNTP newsgroup(s).