Lines Matching refs:with

9 - the VM subsystem that provides allocations at the granularity of pages (with
65    made with `Z_WAITOK` from regular (non exhaustible) zones, or from `kalloc*`
66    interfaces with a size smaller than `KALLOC_SAFE_ALLOC_SIZE`,
83   from other types (typically `zone_require` will be used with this zone),
99 one of its variants (like IOKit's `IOMallocData`). However, this comes with
117 types or structure members can be decorated with `__kernel_ptr_semantics`
139 These come in two variants: arrays, and arrays prefixed with a header.
145 The following rules are expected when dealing with variable sized allocations:
151 If those rules can't be followed, then the allocation must be split with
157 When allocating untyped memory with the data APIs ensure that it doesn't
271 `kfree_data_counted_by` and `kfree_data_sized_by` are used when working with
272 -fbounds-safety and pointers with __counted_by and __sized_by modifiers,
275 with -fbounds-safety semantics. Please note that arguments are evaluated
277 correct usage of these macros; with -fbounds-safety disabled, engineers are on
286 Most, if not all, C++ objects used in conjuction with IOKit APIs
302 `new/delete` (resp. `new[]/delete[]`) with `IOMallocType/IOFreeType` (resp.
332 their implementation, you can use `IODeclareTypedOperators` paired with
361 of the structure, making it relatively easy to attack with