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'.
96 	now exists at virtual address "address" for address space
105 is changing an existing virtual-->physical mapping to a new value,
122 a virtual-->physical translation to exist for a virtual address
123 when that virtual address is flushed from the cache.  The HyperSparc
129 indexed caches which must be flushed when virtual-->physical
161 	Here we are flushing a specific range of (user) virtual
163 	entries in the cache for 'vma->vm_mm' for virtual addresses in
191 	'vma->vm_mm' for virtual address 'addr' which translates
203 	the kernel virtual address range PKMAP_ADDR(0) to
212 	of (kernel) virtual addresses from the cache.  After running,
214 	space for virtual addresses in the range 'start' to 'end-1'.
222 The biggest problem is that of virtual aliasing in the data cache
225 Is your port susceptible to virtual aliasing in its D-cache?
249 maps this page at its virtual address.
259 	kernel virtual addresses during the copy.  The virtual address
261 	load/store instructions happen to virtual addresses which are
265 	The 'addr' parameter tells the virtual address where the
294 	page at the page->virtual mapping of that page.  It is important to
386        flushes the kernel cache for a given virtual address range in
395        the cache for a given virtual address range in the vmap area