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
64 	Primarily, this is used for munmap() type operations.
78 	test (vma->vm_flags & VM_EXEC) to see if this region is
82 	After running, this interface must make sure that any previous
93 	At the end of every page fault, this routine is invoked to
98 	A port may use this information in any way it so chooses.
99 	For example, it could use this event to pre-load TLB
101 	The sparc64 port currently does this.
111 	that uses this interface.
129 The cache level flush will always be first, because this allows
133 cpu is one such cpu with this attribute.
176 	Primarily, this is used for munmap() type operations.
190 	test (vma->vm_flags & VM_EXEC) to see if this region is
194 	The 'pfn' indicates the physical page frame (shift this value
196 	translates to.  It is this mapping which should be removed from
237 physical address from existing at once, you have this problem.
239 If your D-cache has this problem, first define asm/shmparam.h SHMLBA
244 this value.
247 one way to solve this (in particular SPARC_FLAG_MMAPSHARED).
256 maps this page at its virtual address.
270 	for example, uses this technique.
273 	user will ultimately have this page mapped, and the 'page'
283 	user space shared/writable mappings of this page potentially
284 	exist, this routine is called.
290 	      this interface at all.
300 	which have shared+writable mappings of this file, we must make
304 	If D-cache aliasing is not an issue, this routine may
309 	for pagecache pages, it will clear this bit when such
315 	mapping this page.  See sparc64's flush_dcache_page and
317 	about doing this.
322 	made of this flag bit, and if set the flush is done and the flag
329 			to deal with this.
350 	page, it calls this function (currently only
359 	with kmap, it calls this function after all modifications are
365 	architectures.  On incoherent architectures, this should flush
371 	out of (eg when loading modules), this function is called.
373 	If the icache does not snoop stores then this routine will need
379 	is to remove this interface completely.
387 coherency.  It must do this by flushing the vmap range before doing
394        page.  The design is to make this area safe to perform I/O on.
395        Note that this API does *not* also flush the offset map alias