All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	SGI MIPS list <linux-mips@oss.sgi.com>
Subject: Re: [PATCH] Bring back R4600 V1.7 support
Date: Tue, 20 Aug 2002 16:03:11 +0200	[thread overview]
Message-ID: <20020820160311.A26912@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1020820153410.8700F-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Aug 20, 2002 at 03:55:34PM +0200

On Tue, Aug 20, 2002 at 03:55:34PM +0200, Maciej W. Rozycki wrote:

>  An additional thought that just came to my mind: it might be possible to
> avoid masking interrupts with a dummy ll/sc pair only checking if an
> interrupt happened within the critical code.  It should be easy to
> validate since only a single mask of a processor would make use of the
> code.  The real question is: "Do the affected cache operations corrupt any
> state or do they only work on wrong lines?"  If the latter, the approach
> should work for all operations except from "Hit_Invalidate_D" that
> corrupts state by definition (but it isn't used by any R4k processor, so
> it may simply be replaced with a panic()).  Unfortunately, the knowledge
> does no longer exist within IDT, but maybe someone else knows? 

I was thinking about that already but the erratas don't provide enough
details.  The only problem I can see is that ll/sc are fairly slow on some
architectures.  They're supposed to be quite light according to the docs
but in reality I benchmarked ~ 13 cycles for a spinlock on a R10000 and
~ 44 on a more recent chip.

  Ralf

  reply	other threads:[~2002-08-20 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  0:28 [PATCH] Bring back R4600 V1.7 support Jan-Benedict Glaw
2002-08-20 11:33 ` Jan-Benedict Glaw
2002-08-20 13:30   ` Maciej W. Rozycki
2002-08-20 13:55     ` Maciej W. Rozycki
2002-08-20 14:03       ` Ralf Baechle [this message]
2002-08-20 14:36         ` Maciej W. Rozycki
2002-08-20 14:10     ` Jan-Benedict Glaw
2002-08-20 14:46       ` Maciej W. Rozycki

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=20020820160311.A26912@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-mips@oss.sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.