Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/3] fixed mtc0_tlbw_hazard
Date: Mon, 25 Sep 2006 15:28:06 +0100	[thread overview]
Message-ID: <20060925142805.GF20048@linux-mips.org> (raw)
In-Reply-To: <4512C55A.6070206@ru.mvista.com>

On Thu, Sep 21, 2006 at 09:01:14PM +0400, Sergei Shtylyov wrote:

>    I fail to see what was changed WRT SB1 CPUs by the suspected patch. 
>    Though wait... the previous version was inconsistent, using the different 
> barrier definitions for C and assembly (nops in the former, and branch in 
> the latter). But since the assembly version was not really used, it 
> couldn't break anything... :-/
> 
>    Anyway, shouldn't ssnop's be used for SB1 instead? CPU has quad-issue 
> pipeline, hasn't it?

SB1 is almost fully interlocked so the right thing to do is doing nothing.

  Ralf

  parent reply	other threads:[~2006-09-25 14:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 16:07 [PATCH 1/3] fixed mtc0_tlbw_hazard Yoichi Yuasa
2006-09-21 16:10 ` [PATCH 2/3] fixed typo in hazard.h Yoichi Yuasa
2006-09-21 16:13   ` [PATCH 3/3] remove some redefinitions " Yoichi Yuasa
2006-09-25 15:14     ` Ralf Baechle
2006-09-25 14:49   ` [PATCH 2/3] fixed typo " Ralf Baechle
2006-09-21 16:22 ` [PATCH 1/3] fixed mtc0_tlbw_hazard Sergei Shtylyov
2006-09-21 16:41   ` Yoichi Yuasa
2006-09-21 17:01     ` Sergei Shtylyov
2006-09-22  3:17       ` Yoichi Yuasa
2006-09-25 14:28       ` Ralf Baechle [this message]
2006-09-25 14:26     ` Ralf Baechle
2006-09-22  5:16 ` Atsushi Nemoto
2006-09-22  5:47   ` Yoichi Yuasa
2006-09-25 14:24 ` 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=20060925142805.GF20048@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=sshtylyov@ru.mvista.com \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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