platydoc-data/xnu/osfmk/vm/vm_map.c
23,420 lines · · Source index
Referenced in 34 chapters
- Source-reference index
- VM maps, entries and the storage behind an address range
- Pmap and ARM64 translation storage
- Memory-entry capabilities and VM copy storage
- ASTs: pending work, safe service points, and return-to-user control
- AST flavor reference: every bit and its consumer
- Virtual memory and kernel allocation
- Memory mapping from API request to CPU access
- Maps and faults: a reading guide
- Virtual address maps: intervals, ownership, locking, and mutation
- VM API arguments: arithmetic, compatibility and map authority
- Executable memory: mapping admission, protection changes, and ARM64 faults
- MTE tag storage and the physical-page lifecycle
- Fault resolution: from an address to a usable translation
- Pmap fundamentals through concrete address translations
- Wiring, memory entries, and VM transfers
- Copy-overwrite, remapping and mixed page sizes
- Shared regions and transforming pagers
- Reclamation, compression, swap, and process memory policy
- Purgeable objects, aging tokens and owner accounting
- Memorystatus selection, freezing, and recovery
- Kernel virtual allocation: placement, guard objects, and page ownership
- Complex messages: aliasing, memory transfer and partial copyout
- Mach messages: mach_vm
- Mach messages: vm32_map
- Mach messages: vm_map
- From an attached signature to executable mappings and process policy
- Process code-signing controls and ARM64 CSR policy
- TXM: signatures, protected ownership, and executable mappings
- ARM64 bootstrap memory, ownership and lockdown
- Operations across subsystem boundaries
- A mapped file from descriptor lookup to an ARM64 private write
- Concurrent operations: revalidation, namespace death and callback teardown
- An ARM64 configuration and MIG contract walkthrough
Loading source…