Lines Matching refs:that

12 implementation, and what is to happen on that single processor.  The
13 SMP cases are a simple extension, in that you just extend the
14 definition such that the side effect for a particular interface occurs
18 if it can be proven that a user address space has never executed
20 for this address space on that cpu.
25 page tables.  Meaning that if the software page tables change, it is
43 	the TLB.  After running, this interface must make sure that
57 	interface must make sure that any previous page table
66 	The interface is provided in hopes that the port can find
82 	After running, this interface must make sure that any previous
94 	tell the architecture specific code that a translation
111 	that uses this interface.
132 when that virtual address is flushed from the cache.  The HyperSparc
136 to the extent that it is necessary for a particular cpu.  Mostly,
178 	The interface is provided in hopes that the port can find
195 	left by PAGE_SHIFT to get the physical address) that 'addr'
231 The biggest problem is that of virtual aliasing in the data cache
250 other cases.  Please keep in mind that fact that, for a given page
252 mapping, that of the kernel in its linear mapping starting at
267 	for these two pages is chosen in such a way that the kernel
293 	specifically, that the kernel executes store instructions
294 	that dirty data in that page at the page->virtual mapping
295 	of that page.  It is important to flush here to handle
297 	visible to user space mappings of that page.
301 	sure that kernel reads of these pages will see the most recent
305 	simply be defined as a nop on that architecture.
308 	"architecture private".  The kernel guarantees that,
326 			that the actual flush occurs on the same CPU
342 	that need to occur should happen here.  If the processor's
344 	likely that you will need to flush the instruction cache
361 	page up to date.  It is assumed here that the user has no
370   	When the kernel stores into addresses that it will execute
384 subsystem assumes that the user mapping and kernel offset mapping are
392        the vmap area.  This is to make sure that any data the kernel
395        Note that this API does *not* also flush the offset map alias