From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] Cobalt IRQ handler CP0 interlock?
Date: Fri, 21 Feb 2003 13:23:14 +0100 [thread overview]
Message-ID: <20030221132314.A28300@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030221125800.13836I-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Fri, Feb 21, 2003 at 01:11:58PM +0100
On Fri, Feb 21, 2003 at 01:11:58PM +0100, Maciej W. Rozycki wrote:
> > > Does Cobalt have a processor that implements its pipeline differently or
> > > interlocks on CP0 loads? If not, I'll apply the following fix.
> >
> > Mfc0 doesn't need a nops on any R4000 class CPU I know of.
>
> Well, my MIPS R4k manual is vague on this matter and my IDT software
> manual for R3k, R4k, R5k is even explicit on the load delay slot of mfc0.
> But a run-time test proves otherwise.
>
> I stand corrected then unless someone finds a counter-example.
All I can say it's working fine like this since 1984 for R4000 class CPUs.
Ralf
next prev parent reply other threads:[~2003-02-21 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 17:31 [patch] Cobalt IRQ handler CP0 interlock? Maciej W. Rozycki
2003-02-20 18:53 ` Ralf Baechle
2003-02-21 12:11 ` Maciej W. Rozycki
2003-02-21 12:23 ` Ralf Baechle [this message]
2003-02-21 12:41 ` Maciej W. Rozycki
2003-02-21 12:46 ` Ralf Baechle
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=20030221132314.A28300@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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