Lines Matching refs:this

15 on all processors in the system.  Don't let this scare you into
16 thinking SMP cache/tlb flushing must be so inefficient, this is in
20 for this address space on that cpu.
26 possible for stale translations to exist in this "TLB" cache.
33 	The most severe flush of all.  After this interface runs,
43 	the TLB.  After running, this interface must make sure that
56 	address translations from the TLB.  After running, this
63 	Primarily, this is used for munmap() type operations.
77 	test (vma->vm_flags & VM_EXEC) to see if this region is
81 	After running, this interface must make sure that any previous
101    Sparc64 is one example of a platform which does this.
115 	At the end of every page fault, this routine is invoked to
120 	A port may use this information in any way it so chooses.
121 	For example, it could use this event to pre-load TLB
123 	The sparc64 port currently does this.
141 The cache level flush will always be first, because this allows
145 cpu is one such cpu with this attribute.
160 	The most severe flush of all.  After this interface runs,
184 	Primarily, this is used for munmap() type operations.
198 	test (vma->vm_flags & VM_EXEC) to see if this region is
215 physical address from existing at once, you have this problem.
217 If your D-cache has this problem, first define asm/shmparam.h SHMLBA
222 this value.
225 one way to solve this (in particular SPARC_FLAG_MMAPSHARED).
234 maps this page at its virtual address.
236 First, I describe the old method to deal with this problem.  I am
245 	stores done recently by the kernel into this physical
247 	you must flush this page from the D-cache.
250 	any) for this physical page must be written back to main
253 Admittedly, the author did not think very much when designing this
257 deal with D-cache aliasing are meant to address this by telling the
275 	for example, uses this technique.
278 	user will ultimately have this page mapped.
287 	user space shared/writable mappings of this page potentially
288 	exist, this routine is called.
294 	      this interface at all.
304 	which have shared+writable mappings of this file, we must make
308 	If D-cache aliasing is not an issue, this routine may
313 	for pagecache pages, it will clear this bit when such
319 	mapping this page.  See sparc64's flush_dcache_page and
321 	about doing this.
326 	update_mmu_cache(), a check is made of this flag bit, and if
333 			to deal with this.
337 	out of (eg when loading modules), this function is called.
339 	If the icache does not snoop stores then this routine will need
350 	not cross a page boundary.  Currently this is only called from