Lines Matching refs:read

3 Allocating read-only data in xnu.
8 "read-only" allocations.  Data allocated from a read-only zone can only be
29 frequent, fast and easy read/write access to memory.  Unfortunately, these are
43 Data under the control of the Read-Only Allocator can be read from just as
56 1. Pointers to read-only elements should either reside in read-only memory
58 2. Where there is a 1:1 mapping between read/write and read-only elements, the
59    read-only element should include a pointer back to the read/write side (a
60    "back reference") that is validated when traversing from read/write to
61    read-only.
68 On Point 2: by storing a back reference on the read-only side of 1:1
84 Read-only zones cannot be created after lockdown.  To create a new read-only
89 We require identifiers for read-only zones for two reasons: firstly to ensure
91 read-only, and secondly to allow for more stringent validation at the API
94 Once a read-only zone is created, the API for using it is small and simple.
97 - `zalloc_ro`: Allocate an element from a read-only zone.
98 - `zfree_ro`: Free an element back to a read-only zone.  Note that this is a
100 - `zone_require_ro`: Verify that an element belongs to a given read-only zone
102 - `zalloc_ro_mut`: Modify part of an element allocated from a read-only zone.