25-akpm/Documentation/cachetlb.txt | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff -puN Documentation/cachetlb.txt~flush-invalidate-fixes-doc-fixes Documentation/cachetlb.txt --- 25/Documentation/cachetlb.txt~flush-invalidate-fixes-doc-fixes Tue Sep 23 14:58:18 2003 +++ 25-akpm/Documentation/cachetlb.txt Tue Sep 23 14:59:17 2003 @@ -59,9 +59,9 @@ changes occur: address translations from the TLB. After running, this interface must make sure that any previous page table modifications for the address space 'vma->vm_mm' in the range - 'start' to 'end' will be visible to the cpu. That is, after + 'start' to 'end-1' will be visible to the cpu. That is, after running, here will be no entries in the TLB for 'mm' for - virtual addresses in the range 'start' to 'end'. + virtual addresses in the range 'start' to 'end-1'. The "vma" is the backing store being used for the region. Primarily, this is used for munmap() type operations. @@ -100,7 +100,7 @@ changes occur: unsigned long start, unsigned long end) The software page tables for address space 'mm' for virtual - addresses in the range 'start' to 'end' are being torn down. + addresses in the range 'start' to 'end-1' are being torn down. Some platforms cache the lowest level of the software page tables in a linear virtually mapped array, to make TLB miss processing @@ -181,7 +181,7 @@ Here are the routines, one by one: Here we are flushing a specific range of (user) virtual addresses from the cache. After running, there will be no entries in the cache for 'vma->vm_mm' for virtual addresses in - the range 'start' to 'end'. + the range 'start' to 'end-1'. The "vma" is the backing store being used for the region. Primarily, this is used for munmap() type operations. @@ -225,7 +225,7 @@ Here are the routines, one by one: Here in these two interfaces we are flushing a specific range of (kernel) virtual addresses from the cache. After running, there will be no entries in the cache for the kernel address - space for virtual addresses in the range 'start' to 'end'. + space for virtual addresses in the range 'start' to 'end-1'. The first of these two routines is invoked after map_vm_area() has installed the page table entries. The second is invoked _