From: "Kevin D. Kissell" <kevink@mips.com>
To: "Greg Weeks" <greg.weeks@timesys.com>,
"Ralf Baechle" <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: another 4kc machine check.
Date: Mon, 11 Apr 2005 22:42:57 +0200 [thread overview]
Message-ID: <007101c53ed7$44a71ae0$10eca8c0@grendel> (raw)
In-Reply-To: 425AD440.5050600@timesys.com
One further comment:
> This patch appears to fix my machine check problem on the 4kc. The 4kc
> shouldn't need an ssnop here, but this appears to fix it.
The 4Kc shouldn't need an ssnop/ehb for the purposes of a *load*, but
if the exception was on an instruction fetch, the documentation is reasonably
clear that there's a hazard of 3 cycles before the new entry can be used for
a fetch - which is what ERET will do in the case of a instruction fetch miss.
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Greg Weeks <greg.weeks@timesys.com>, Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: another 4kc machine check.
Date: Mon, 11 Apr 2005 22:42:57 +0200 [thread overview]
Message-ID: <007101c53ed7$44a71ae0$10eca8c0@grendel> (raw)
Message-ID: <20050411204257.n_MNAgqdn9FfPjnl-vo2bJyl6nWPAsr-X3Y2XBhLOMo@z> (raw)
In-Reply-To: 425AD440.5050600@timesys.com
One further comment:
> This patch appears to fix my machine check problem on the 4kc. The 4kc
> shouldn't need an ssnop here, but this appears to fix it.
The 4Kc shouldn't need an ssnop/ehb for the purposes of a *load*, but
if the exception was on an instruction fetch, the documentation is reasonably
clear that there's a hazard of 3 cycles before the new entry can be used for
a fetch - which is what ERET will do in the case of a instruction fetch miss.
Regards,
Kevin K.
next prev parent reply other threads:[~2005-04-11 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 14:06 another 4kc machine check Greg Weeks
2005-04-08 14:45 ` Greg Weeks
2005-04-08 16:13 ` Ralf Baechle
2005-04-08 16:45 ` Greg Weeks
2005-04-11 19:47 ` Greg Weeks
2005-04-11 20:27 ` Kevin D. Kissell
2005-04-11 20:27 ` Kevin D. Kissell
2005-04-12 14:52 ` Greg Weeks
2005-04-12 15:22 ` Maciej W. Rozycki
2005-04-12 16:38 ` Kevin D. Kissell
2005-04-12 16:38 ` Kevin D. Kissell
2005-04-12 16:52 ` Greg Weeks
2005-04-12 19:12 ` Greg Weeks
2005-04-11 20:42 ` Kevin D. Kissell [this message]
2005-04-11 20:42 ` Kevin D. Kissell
2005-06-10 16:39 ` Chris Wedgwood
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='007101c53ed7$44a71ae0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=greg.weeks@timesys.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