Lines Matching refs:virtual

24 virtual-->physical address translations obtained from the software
55 	Here we are flushing a specific range of (user) virtual
60 	there will be no entries in the TLB for 'mm' for virtual
83 	user virtual address 'page' will be visible to the cpu.  That
85 	'vma->vm_mm' for virtual address 'page'.
92    The software page tables for address space 'mm' for virtual
103    Usually, when munmap()'ing an area of user virtual address
117 	described by "pte" now exists at virtual address "address"
126 is changing an existing virtual-->physical mapping to a new value,
143 a virtual-->physical translation to exist for a virtual address
144 when that virtual address is flushed from the cache.  The HyperSparc
150 indexed caches which must be flushed when virtual-->physical
179 	Here we are flushing a specific range of (user) virtual
181 	entries in the cache for 'mm' for virtual addresses in the
203 	'vma->vm_mm' for virtual address 'page'.
209 The biggest problem is that of virtual aliasing in the data cache
212 Is your port susceptible to virtual aliasing in it's D-cache?
234 maps this page at its virtual address.
271 	kernel virtual addresses during the copy.  The virtual address
273 	load/store instructions happen to virtual addresses which are
277 	The "address" parameter tells the virtual address where the
298 	that dirty data in that page at the page->virtual mapping
347 	gives the virtual address in that process's address space,