Lines Matching full:set

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
11 matches the tag set by the application. In case of mismatch, processor
16 1. Set the user mode PSTATE.mcde bit. This acts as master switch for
19 2. Set TTE.mcd bit on any TLB entries that correspond to the range of
21    on the pages that have TTE.mcd bit set.
23 3. Set the version tag for virtual addresses using stxa instruction
26    be repeated for entire page to set tags for entire page.
31 version tag has been set for a memory location, the tag is stored in the
39 ADI is enabled on a set of pages using mprotect() with PROT_ADI flag.
40 When ADI is enabled on a set of pages by a task for the first time,
42 addresses are set with an stxa instruction on the addresses using
61 - Version tags are set on virtual addresses from userspace even though
62   tags are stored in physical memory. Tags are set on a physical page
66 - When a task frees a memory page it had set version tags on, the page
70   freed and allocated back to the same task, old version tags set by the
75 - Kernel does not set any tags for user pages and it is entirely a
76   task's responsibility to set any version tags. Kernel does ensure the
83   range, enable ADI on the range using mprotect() and set version tags
87 - ADI tags can only be set on writable memory. For example, ADI tags can
88   not be set on read-only mappings.
102 	tag in the address used (bits 63:60) does not match the tag set on
122 	tag in the address used (bits 63:60) does not match the tag set on
142 	When a task has not enabled ADI and attempts to set ADI version
146 	fault type set to 0xa (invalid ASI). When this occurs, the kernel
231           /* Set the ADI version tag on the shm segment