Home
last modified time | relevance | path

Searched refs:three (Results 1 – 9 of 9) sorted by relevance

/xnu-12377.1.9/doc/debugging/
H A Dmacro_testing.md49 A test developer has three options how to handle mocking in a test:
/xnu-12377.1.9/tests/vm/
H A Dconfigurator_test.c835 mach_vm_address_t three = two + entry_size; in test_shared_entry_pairs() local
836 mach_vm_address_t four = three + entry_size; in test_shared_entry_pairs()
839 test_one_shared_pair(checker_list, two, three, entry_size, 0); in test_shared_entry_pairs()
/xnu-12377.1.9/doc/observability/
H A Drecount.md109 Since three entities need to be updated at once (thread, task, and processor), only the last update…
/xnu-12377.1.9/doc/mach_ipc/
H A Dkmsg.md416 interact with Mach is via three calls:
/xnu-12377.1.9/doc/building/
H A Dxnu_build_consolidation.md13 Given the time it takes to compile all three different variants (release, debug and development) fo…
/xnu-12377.1.9/doc/vm/
H A Dmemorystatus.md149 NB: There are technically three memorystatus threads: `VM_memorystatus_1`, `VM_memorystatus_2`, and…
H A Dsanitize.md40 VM functions can be called from three places: userspace, kexts, and xnu itself.
/xnu-12377.1.9/makedefs/
H A DMakeInc.top108 # Target configs come in groups of three parameters. The first is the
/xnu-12377.1.9/tools/lldbmacros/
H A Dmemory.py4005 three = two ^ bucket_hash
4006 four = one + three