Lines Matching refs:version

6 ADI allows a task to set version tags on any subset of its address
7 space. Once ADI is enabled and version tags are set for ranges of
9 to memory in these ranges to the version set by the application
20    addresses ADI is being enabled on. MMU checks the version tag only
23 3. Set the version tag for virtual addresses using stxa instruction
30 top bits in the virtual address that specify the version tag.  Once
31 version tag has been set for a memory location, the tag is stored in the
32 physical memory and the same tag must be present in the ADI version tag
34 SPARC M7 processor, MMU uses bits 63-60 for version tags and ADI block
36 version to, say 10, on a range of memory, must access that memory using
51 	AT_ADI_NBITS	Number of ADI version bits in the VA
66 - When a task frees a memory page it had set version tags on, the page
69   version tags as well for the page. If a page allocated to a task is
70   freed and allocated back to the same task, old version tags set by the
76   task's responsibility to set any version tags. Kernel does ensure the
77   version tags are preserved if a page is swapped out to the disk and
78   swapped back in. It also preserves that version tags if a page is
83   range, enable ADI on the range using mprotect() and set version tags
142 	When a task has not enabled ADI and attempts to set ADI version
188           int shmid, version;
231           /* Set the ADI version tag on the shm segment
233           version = 10;
240                           : "r" (tmp_addr), "r" (version));
246 	 * version tag in the upper adi_nbits bits
250           veraddr = (void *) (((unsigned long)version << (64-adi_nbits))