diff options
author | Benjamin Herrenschmidt <benh@au1.ibm.com> | 2006-05-30 14:14:19 +1000 |
---|---|---|
committer | Paul Mackerras <paulus@samba.org> | 2006-06-09 21:20:59 +1000 |
commit | c5cf0e30bf3d8cb56758abb612827647c0a821cf (patch) | |
tree | 54a471818e91204db11f14544df0bb38bd03058f /lib/ts_bm.c | |
parent | a5bba930d802009c259e56c8d53086d96f63813b (diff) |
[PATCH] powerpc: Fix buglet with MMU hash management
Our MMU hash management code would not set the "C" bit (changed bit) in
the hardware PTE when updating a RO PTE into a RW PTE. That would cause
the hardware to possibly to a write back to the hash table to set it on
the first store access, which in addition to being a performance issue,
might also hit a bug when running with native hash management (non-HV)
as our code is specifically optimized for the case where no write back
happens.
Thus there is a very small therocial window were a hash PTE can become
corrupted if that HPTE has just been upgraded to read write, a store
access happens on it, and that races with another processor evicting
that same slot. Since eviction (caused by an almost full hash) is
extremely rare, the bug is very unlikely to happen fortunately.
This fixes by allowing the updating of the protection bits in the native
hash handling to also set (but not clear) the "C" bit, and, in order to
also improve performances in the general case, by always setting that
bit on newly inserted hash PTE so that writeback really never happens.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'lib/ts_bm.c')
0 files changed, 0 insertions, 0 deletions