Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Adam Kiepul <Adam_Kiepul@pmc-sierra.com>
Cc: "'hadi@cyberus.ca'" <hadi@cyberus.ca>,
	linux-mips@linux-mips.org, sibyte-users@bitmover.com
Subject: Re: [SiByte] RE: weird sb1250 behavior
Date: Fri, 28 May 2004 22:59:23 +0200	[thread overview]
Message-ID: <20040528205923.GA14682@linux-mips.org> (raw)
In-Reply-To: <9DFF23E1E33391449FDC324526D1F2590283C58B@sjc1exm02.pmc_nt.nt.pmc-sierra.bc.ca>

On Fri, May 28, 2004 at 01:11:38PM -0700, Adam Kiepul wrote:

> There is a possible cache line read-after-write pseudo-dependency that, along with the code alignment in terms of the instruction pair doublewords, may do something weird to the sb1250 pipeline. Just my guess.

memcpy's source deals with what probably is another instance of the same
effect:

#ifdef CONFIG_CPU_SB1
        nop                             # improves slotting
#endif

  Ralf

      reply	other threads:[~2004-05-28 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 20:11 weird sb1250 behavior Adam Kiepul
2004-05-28 20:59 ` Ralf Baechle [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=20040528205923.GA14682@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Adam_Kiepul@pmc-sierra.com \
    --cc=hadi@cyberus.ca \
    --cc=linux-mips@linux-mips.org \
    --cc=sibyte-users@bitmover.com \
    /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