diff options
author | David Howells <dhowells@redhat.com> | 2010-10-01 10:31:03 +0100 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2010-10-01 15:01:47 -0700 |
commit | 57cf4f78c6266d5a6e5de5485065d4015b84bb30 (patch) | |
tree | 9191fd529acc57ac0b0114f73b675aa99fcfed1f /arch/mn10300/mm/cache-disabled.c | |
parent | 18ffe4b18cef097f789d3ff43b45f2938cebe241 (diff) | |
download | blackbird-op-linux-57cf4f78c6266d5a6e5de5485065d4015b84bb30.tar.gz blackbird-op-linux-57cf4f78c6266d5a6e5de5485065d4015b84bb30.zip |
MN10300: Fix flush_icache_range()
flush_icache_range() is given virtual addresses to describe the region. It
deals with these by attempting to translate them through the current set of
page tables.
This is fine for userspace memory and vmalloc()'d areas as they are governed by
page tables. However, since the regions above 0x80000000 aren't translated
through the page tables by the MMU, the kernel doesn't bother to set up page
tables for them (see paging_init()).
This means flush_icache_range() as it stands cannot be used to flush regions of
the VM area between 0x80000000 and 0x9fffffff where the kernel resides if the
data cache is operating in WriteBack mode.
To fix this, make flush_icache_range() first check for addresses in the upper
half of VM space and deal with them appropriately, before dealing with any
range in the page table mapped area.
Ordinarily, this is not a problem, but it has the capacity to make kprobes and
kgdb malfunction. It should not affect gdbstub, signal frame setup or module
loading as gdb has its own flush functions, and the others take place in the
page table mapped area only.
Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Akira Takeuchi <takeuchi.akr@jp.panasonic.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/mn10300/mm/cache-disabled.c')
0 files changed, 0 insertions, 0 deletions