Searched refs:safe (Results 1 – 13 of 13) sorted by relevance
| /xnu-12377.81.4/iokit/DriverKit/ |
| H A D | IOEventLink.iig | 116 * @discussion This API call is real time safe. 124 * @discussion This API call is real time safe. 132 * @discussion This API call is real time safe. 141 * @discussion This API call is real time safe. 152 * @discussion This API call is real time safe. 171 …he event link must be activated before it can be signaled or waited on. This is not real-time safe. 179 * @discussion The eventlink should be activated before this call. This is not real-time safe. 187 * @brief Disassociate the current thread from the eventlink. This is not real-time safe.
|
| H A D | IOService.iig | 254 …ssion DriverKit notifies of changes in power of a provider. The driver should make itself safe for
|
| /xnu-12377.81.4/doc/primitives/ |
| H A D | string-handling.md | 49 * `strl` functions (strlcpy, strlcat, etc), safe but easily misunderstood. 55 strings (`strlen`, `strcmp`, `strchr`, etc) are generally found to be safe 63 _generally_ safe, but `strncmp` can cause confusion over which string is bound 68 NUL-terminate their output. This makes the writing part safe. (xnu adds `strl` 69 comparison functions, which do no writing and are also safe.) However, these
|
| H A D | atomics.md | 52 The sequentially consistent world is extremely safe from a lot of compiler 372 * This isn't safe, as there's absolutely no hardware dependency involved. 415 **Note**: this technique is NOT safe when the compiler can reason about the
|
| /xnu-12377.81.4/libkern/os/ |
| H A D | log.c | 619 bool safe, bool logging, bool addcr) in _os_log_to_msgbuf_internal() argument 633 if (!bsd_log_lock(safe)) { in _os_log_to_msgbuf_internal() 638 if (!safe) { in _os_log_to_msgbuf_internal() 784 bool safe = os_log_safe(); in _os_log_with_args_internal() local 788 _os_log_to_msgbuf_internal(fmt, args, ts, safe, logging, addcr); in _os_log_with_args_internal() 791 if (safe && logging) { in _os_log_with_args_internal()
|
| /xnu-12377.81.4/osfmk/mach/ |
| H A D | mach_notify.defs | 34 * until the real notify.h becomes "MIG-safe."
|
| H A D | prof.defs | 44 * Merged '64-bit safe' changes from DEC alpha port.
|
| /xnu-12377.81.4/osfmk/kern/ |
| H A D | printf.c | 819 bsd_log_lock(bool safe) in bsd_log_lock() argument 821 if (!safe) { in bsd_log_lock()
|
| /xnu-12377.81.4/doc/vm/ |
| H A D | sanitize.md | 154 - Associate the safe type with its unsafe type using `VM_UNSAFE_TYPE` or 231 return their unwrapped safe values. In this function you should call the 244 - Ensure that you return safe values on failure for all opaque types that 328 them. We reviewed the vm32 implementations and decided they were safe and 333 the trap implementations and decided they were safe and unlikely to do
|
| /xnu-12377.81.4/libkern/zlib/ |
| H A D | README | 4 thread safe. The data format used by the zlib library is described by RFCs
|
| /xnu-12377.81.4/doc/lifecycle/ |
| H A D | hibernation.md | 152 this point. This allows for "safe sleep" where RAM remains powered until the 175 was mapped by the booter is safe to call, since all the other wired pages are
|
| /xnu-12377.81.4/doc/allocators/ |
| H A D | api-basics.md | 303 `IONew/IODelete`) is safe.
|
| /xnu-12377.81.4/doc/arm/ |
| H A D | sme.md | 113 safe way to disable SME prioritization. Otherwise the exact meaning of
|