From: Greg Weeks <greg.weeks@timesys.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: another 4kc machine check.
Date: Tue, 12 Apr 2005 12:52:18 -0400 [thread overview]
Message-ID: <425BFCC2.9060901@timesys.com> (raw)
In-Reply-To: <00c701c53f7e$09ec56c0$10eca8c0@grendel>
Kevin D. Kissell wrote:
>>On Mon, 11 Apr 2005, Kevin D. Kissell wrote:
>>
>>
>>
>>>If the 4KC and 4KEC need it, so does the 4KSC (and 4KSD).
>>>
>>>
>> But that's weird in the first place as 4Kc implements the original
>>revision of MIPS32 so it does not implement "ehb". Therefore it acts just
>>as an ordinary "nop", but according to the 4K manual there is no need for
>>one -- the hazard between a move to EntryLo0/EntryLo1 and tlbwi/tlbwr is
>>explicitly listed as 0 instructions.
>>
>>
>
>Oops. Maybe I misread the patch. I thought the added NOP was between
>the TLBWR and the ERET.
>
>
No, it adds it before the TLBWR where there shouldn't be a hazard.
Greg Weeks
next prev parent reply other threads:[~2005-04-12 16:52 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 [this message]
2005-04-12 19:12 ` Greg Weeks
2005-04-11 20:42 ` Kevin D. Kissell
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=425BFCC2.9060901@timesys.com \
--to=greg.weeks@timesys.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@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