[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20061202094929.GA12294@flint.arm.linux.org.uk>
Date: Sat, 2 Dec 2006 09:49:29 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Linus Torvalds <torvalds@...l.org>
Cc: Ralf Baechle <ralf@...ux-mips.org>,
David Miller <davem@...emloft.net>, nickpiggin@...oo.com.au,
akpm@...l.org, linux-kernel@...r.kernel.org, anemo@....ocn.ne.jp,
linux-arch@...r.kernel.org, schwidefsky@...ibm.com,
James.Bottomley@...elEye.com
Subject: Re: [PATCH 1/3] Fix COW D-cache aliasing on fork
On Fri, Oct 20, 2006 at 05:38:32PM -0700, Linus Torvalds wrote:
> On Sat, 21 Oct 2006, Ralf Baechle wrote:
> > > That said, maybe nobody does that. Virtual caches are a total braindamage
> > > in the first place, so hopefully they have limited use.
> >
> > On MIPS we never had pure virtual caches.
>
> Ok, so on MIPS my schenario doesn't matter.
>
> I think (but may be mistaken) that ARM _does_ have pure virtual caches
> with a process ID, but people have always ended up flushing them at
> context switch simply because it just causes too much trouble.
Just read this, sorry.
The majority of ARM CPU implementations have pure virtual caches
_without_ process IDs. (Some have a nasty hack which involves
remapping the lower 32MB of virtual memory space to other areas
of the cache's virtual space, but obviously that limits you to
32MB of VM.)
Thankfully, with ARM version 6, they had an inkling of clue, and
decided to move to VIPT caches but with _optional_ aliasing, and
if the CPU design was Harvard there's a possibility for D/I cache
aliasing.
> > Be sure I'm sending a CPU designers a strong message about aliases.
>
> Castration. That's the best solution. We don't want those people
> procreating.
Absolutely. Can we start such a program in Cambridge, England ASAP
please?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists