Lines Matching full:virtual

25 virtual-->physical address translations obtained from the software
56 	Here we are flushing a specific range of (user) virtual
62 	virtual addresses in the range 'start' to 'end-1'.
85 	user virtual address 'addr' will be visible to the cpu.  That
87 	'vma->vm_mm' for virtual address 'addr'.
98 	at virtual address "address" for "nr" consecutive pages.
109 is changing an existing virtual-->physical mapping to a new value,
126 a virtual-->physical translation to exist for a virtual address
127 when that virtual address is flushed from the cache.  The HyperSparc
133 indexed caches which must be flushed when virtual-->physical
165 	Here we are flushing a specific range of (user) virtual
167 	entries in the cache for 'vma->vm_mm' for virtual addresses in
195 	'vma->vm_mm' for virtual address 'addr' which translates
207 	the kernel virtual address range PKMAP_ADDR(0) to
216 	of (kernel) virtual addresses from the cache.  After running,
218 	space for virtual addresses in the range 'start' to 'end-1'.
226 The biggest problem is that of virtual aliasing in the data cache
229 Is your port susceptible to virtual aliasing in its D-cache?
253 maps this page at its virtual address.
263 	kernel virtual addresses during the copy.  The virtual address
265 	load/store instructions happen to virtual addresses which are
269 	The 'addr' parameter tells the virtual address where the
298 	page at the kernel virtual mapping of that page.  It is important to
385        flushes the kernel cache for a given virtual address range in
394        the cache for a given virtual address range in the vmap area