Home
last modified time | relevance | path

Searched refs:way (Results 1 – 18 of 18) sorted by relevance

/xnu-8792.41.9/osfmk/kern/
H A Decc.h106 uint32_t way; member
/xnu-8792.41.9/config/
H A DMasterVersion16 # The correct way to make use of the kernel version within kernel code or a
/xnu-8792.41.9/doc/
H A Dxnu_build_consolidation.md43 Although not often, the kernel may still require deriving, one way or another, parameters like cach…
44 and number of set/ways. XNU needs most of this information to perform set/way clean/invalidate oper…
87 early boot. The way these checks are performed varies from feature to feature (for example, VHE is …
H A Datomics.md247 way more readable compare exchange loops. It also uses LL/SC constructs more
298 before the loop should be used in this way:
H A Ddebugging.md16 **xrange** semantics. The simplest solution is to port your code and use Python 3 way:
247 This impacts the way an object is checked for being an integer. Be careful about following construc…
250 # BAD: generally not a good way to do type checking in Python
/xnu-8792.41.9/doc/allocators/
H A Dapi-basics.md36 allocating memory in such a fashion in a very compact way.
71 The first blessed way to allocate memory in the kernel is by using zones.
94 blessed way to allocate typed memory in XNU is using the typed allocator
369 The blessed way of wrapping and passing a C++ type allocation for use in the
H A Dread-only.md22 bypasses obstacles standing in the way of the desired data.
/xnu-8792.41.9/tools/lldbmacros/
H A DREADME.md26 lldb can be used for kernel debugging the same way as gdb. The simplest way is to start lldb with k…
149 The python modules are designed in such a way that the command from lldb invokes a python function …
203 …s are important based on some flag or value in some field or variable. The way it works is every t…
293 … This way the expressing withing ` ` is evaluated by lldb and the value is passed to the command.
/xnu-8792.41.9/tools/tests/perf_index/
H A DREADME78 By default xnu builds all-way fat, but you can restrict this by explicitly
/xnu-8792.41.9/osfmk/tests/
H A DREADME.md77 …* T_ASSERT macros will check for condition and upon failure return with KERN_FAILURE. This way it …
/xnu-8792.41.9/osfmk/mach/
H A Dhost_priv.defs163 * normal way, via vm_deallocate.
/xnu-8792.41.9/bsd/man/man2/
H A Dgetdirentriesattr.2125 packed in exactly the same way as they are returned from
/xnu-8792.41.9/makedefs/
H A DMakeInc.kernel245 # a way of retrieving these counters from LAST anyway, so there's no harm in just
/xnu-8792.41.9/doc/memorystatus/
H A Doverview.md161 When awoken it calls `consider_vm_pressure_events` which winds its way to `memorystatus_update_vm_p…
H A Dfreezer.md68 …goes to band 75 instead of band 0. Aside from process termination the only way out of the freezer …
/xnu-8792.41.9/iokit/DriverKit/
H A DIOService.iig323 …* The best way by far to handle this is to change how you schedule your time-critical DMA ope…
/xnu-8792.41.9/
H A DAPPLE_LICENSE36 part of a Larger Work, in any way to provide a service, including but
/xnu-8792.41.9/tests/
H A Dstackshot_tests.m2152 // having a way to verify that the coreanalytics event was received would be even better