.. | .. |
---|
101 | 101 | translations for software managed TLB configurations. |
---|
102 | 102 | The sparc64 port currently does this. |
---|
103 | 103 | |
---|
104 | | -6) ``void tlb_migrate_finish(struct mm_struct *mm)`` |
---|
105 | | - |
---|
106 | | - This interface is called at the end of an explicit |
---|
107 | | - process migration. This interface provides a hook |
---|
108 | | - to allow a platform to update TLB or context-specific |
---|
109 | | - information for the address space. |
---|
110 | | - |
---|
111 | | - The ia64 sn2 platform is one example of a platform |
---|
112 | | - that uses this interface. |
---|
113 | | - |
---|
114 | 104 | Next, we have the cache flushing interfaces. In general, when Linux |
---|
115 | 105 | is changing an existing virtual-->physical mapping to a new value, |
---|
116 | 106 | the sequence will be in one of the following forms:: |
---|
.. | .. |
---|
223 | 213 | there will be no entries in the cache for the kernel address |
---|
224 | 214 | space for virtual addresses in the range 'start' to 'end-1'. |
---|
225 | 215 | |
---|
226 | | - The first of these two routines is invoked after map_vm_area() |
---|
| 216 | + The first of these two routines is invoked after map_kernel_range() |
---|
227 | 217 | has installed the page table entries. The second is invoked |
---|
228 | 218 | before unmap_kernel_range() deletes the page table entries. |
---|
229 | 219 | |
---|