Lines Matching refs:virtual

24 virtual-->physical address translations obtained from the software
55 	Here we are flushing a specific range of (user) virtual
61 	virtual addresses in the range 'start' to 'end-1'.
84 	user virtual address 'addr' will be visible to the cpu.  That
86 	'vma->vm_mm' for virtual address 'addr'.
95 	now exists at virtual address "address" for address space
114 is changing an existing virtual-->physical mapping to a new value,
131 a virtual-->physical translation to exist for a virtual address
132 when that virtual address is flushed from the cache.  The HyperSparc
138 indexed caches which must be flushed when virtual-->physical
170 	Here we are flushing a specific range of (user) virtual
172 	entries in the cache for 'vma->vm_mm' for virtual addresses in
200 	'vma->vm_mm' for virtual address 'addr' which translates
212 	the kernel virtual address range PKMAP_ADDR(0) to
221 	of (kernel) virtual addresses from the cache.  After running,
223 	space for virtual addresses in the range 'start' to 'end-1'.
231 The biggest problem is that of virtual aliasing in the data cache
234 Is your port susceptible to virtual aliasing in its D-cache?
256 maps this page at its virtual address.
266 	kernel virtual addresses during the copy.  The virtual address
268 	load/store instructions happen to virtual addresses which are
272 	The 'addr' parameter tells the virtual address where the
294 	that dirty data in that page at the page->virtual mapping
391        flushes the kernel cache for a given virtual address range in
399        the cache for a given virtual address range in the vmap area