All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Virtual alias cache coherency results (was: x86, ARM, PARISC, PPC, MIPS and Sparc folks please run this)
Date: Wed, 10 Sep 2003 23:39:51 +0100	[thread overview]
Message-ID: <20030910233951.Q30046@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030910210416.GA24258@mail.jlokier.co.uk>; from jamie@shareable.org on Wed, Sep 10, 2003 at 10:04:16PM +0100

On Wed, Sep 10, 2003 at 10:04:16PM +0100, Jamie Lokier wrote:
> Write buffers
> .............
> 
> It was a surprise to discover CPUs which have incoherent write buffers
> yet have coherent L1 caches.  (This means that a write to a virtual
> address which is read from within very few instructions returns the
> written data, completely ignoring any intervening write instructions
> which write to a different virtual address which maps to the same
> memory location.)  I didn't exect to find any of these.
> 
>     CPUs with incoherent write buffers: PA-RISC 2.0, 68040 and ARMs.

Some StrongARM CPUs seem to exhibit non-coherence in their write buffers.
I don't think we've done enough testing to make any statement like "ARMs
have uncoherent write buffers."

Tests need to be run on a larger proportion of the following:

*	ARM720
	ARM920
	ARM922
	ARM925
	ARM926
	ARM1020
	ARM1022
	ARM1026
*	StrongARM-110	(DEC/Intel)
	StrongARM-1100	(DEC/Intel)
*	StrongARM-1110	(Intel)
*	Xscale		(Intel)
	PXA		(Intel)

And so far, there are only results for 4 of these devices, with some
revisions of StrongARM-110's passing and others failing.

> Validity of SHMLBA value
> ........................
> 
>     SHMLBA not valid:		ARM, m68k
> 
> Note that "SHMLBA" is defined for some architectures on which it
> doesn't actually provide coherent virtual aliases.  On the ARM this is
> believed to be due to a chip bug, and very recent kernels may contain
> a workaround for it (disabling the write buffer for aliased pages).

Not correct.  Because of the fundamental nature of VIVT caches, there
is no "SHMLBA" value which prevents aliases occuring.  Think carefully
about the structure of a VIVT cache and how it would be searched.  This
isn't a chip bug.

The kernel works around this, but, due to some bugs on StrongARM chips
in the write buffer, it appears that we need further work-arounds, which
are already implemented.

-- 
Russell King (rmk@arm.linux.org.uk)	http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
  2.6 ARM Linux   - http://www.arm.linux.org.uk/
  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
  2.6 Serial core

  reply	other threads:[~2003-09-10 22:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 21:04 Virtual alias cache coherency results (was: x86, ARM, PARISC, PPC, MIPS and Sparc folks please run this) Jamie Lokier
2003-09-10 22:39 ` Russell King [this message]
2003-09-10 23:37   ` Jamie Lokier
2003-09-11  0:07     ` Russell King
2003-09-11 12:35       ` Jamie Lokier
2003-09-11 15:09         ` Russell King
2003-09-11 16:25           ` Jamie Lokier
2003-09-11 16:52             ` Russell King
2003-09-11 18:55               ` Jamie Lokier
2003-09-12  0:45               ` Jamie Lokier
2003-09-12  7:48                 ` Russell King
2003-09-11 18:51   ` Guennadi Liakhovetski
2003-09-11 10:17 ` Richard Curnow
2003-09-11 16:34   ` Jamie Lokier

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=20030910233951.Q30046@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.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 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.