| /openbmc/linux/tools/perf/util/ |
| H A D | bpf-utils.h | 15 * struct bpf_prog_info has multiple arrays. The user has option to choose
16 * arrays to fetch from kernel. The following APIs provide an uniform way to
17 * fetch these data. All arrays in bpf_prog_info are stored in a single
28 * __u64 arrays = (1UL << PERF_BPIL_MAP_IDS) |
31 * get_bpf_prog_info_linear(fd, arrays);
60 /* which arrays are included in data */
61 __u64 arrays; member
67 get_bpf_prog_info_linear(int fd, __u64 arrays);
|
| H A D | bpf-utils.c | 111 get_bpf_prog_info_linear(int fd, __u64 arrays) in get_bpf_prog_info_linear() argument
120 if (arrays >> PERF_BPIL_LAST_ARRAY) in get_bpf_prog_info_linear()
130 /* step 2: calculate total size of all arrays */ in get_bpf_prog_info_linear()
132 bool include_array = (arrays & (1UL << i)) > 0; in get_bpf_prog_info_linear()
145 arrays &= ~(1UL << i); /* clear the bit */ in get_bpf_prog_info_linear()
161 info_linear->arrays = arrays; in get_bpf_prog_info_linear()
169 if ((arrays & (1UL << i)) == 0) in get_bpf_prog_info_linear()
185 /* step 5: call syscall again to get required arrays */ in get_bpf_prog_info_linear()
198 if ((arrays & (1UL << i)) == 0) in get_bpf_prog_info_linear()
230 if ((info_linear->arrays & (1UL << i)) == 0) in bpil_addr_to_offs()
[all …]
|
| H A D | bpf-event.c | 180 u64 arrays; in perf_event__synthesize_one_bpf_prog() local
188 arrays = 1UL << PERF_BPIL_JITED_KSYMS; in perf_event__synthesize_one_bpf_prog()
189 arrays |= 1UL << PERF_BPIL_JITED_FUNC_LENS; in perf_event__synthesize_one_bpf_prog()
190 arrays |= 1UL << PERF_BPIL_FUNC_INFO; in perf_event__synthesize_one_bpf_prog()
191 arrays |= 1UL << PERF_BPIL_PROG_TAGS; in perf_event__synthesize_one_bpf_prog()
192 arrays |= 1UL << PERF_BPIL_JITED_INSNS; in perf_event__synthesize_one_bpf_prog()
193 arrays |= 1UL << PERF_BPIL_LINE_INFO; in perf_event__synthesize_one_bpf_prog()
194 arrays |= 1UL << PERF_BPIL_JITED_LINE_INFO; in perf_event__synthesize_one_bpf_prog()
196 info_linear = get_bpf_prog_info_linear(fd, arrays); in perf_event__synthesize_one_bpf_prog()
455 u64 arrays; in perf_env__add_bpf_info() local
[all …]
|
| /openbmc/linux/scripts/coccinelle/misc/ |
| H A D | flexible_array.cocci | 3 /// Zero-length and one-element arrays are deprecated, see
75 // handling of bitfields, arrays, etc.
99 …https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)"
106 …https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)"
|
| /openbmc/linux/drivers/usb/gadget/function/ |
| H A D | u_uvc.h | 38 * uvc_ss_control_cls arrays respectively. Legacy gadgets must
46 * super-speed. They will point to the uvc_[fhs]s_streaming_cls arrays
60 * Control descriptors pointers arrays for full-/high-speed and
78 * arrays are allocated at runtime as the number of descriptors isn't
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | md.rst | 1 RAID arrays
4 Boot time assembly of RAID arrays
14 for old raid arrays without persistent superblocks::
18 for raid arrays with persistent superblocks::
77 Boot time autodetection of RAID arrays
81 type 0xfd are scanned and automatically assembled into RAID arrays.
87 that all auto-detected arrays are assembled as partitionable.
89 Boot time assembly of degraded/dirty arrays
108 arrays to be started.
165 Specific Rules that apply to format-0 super block arrays, and arrays with no superblock (non-persis…
[all …]
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | argument.hpp | 31 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
38 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
46 // NOLINTNEXTLINE(cppcoreguidelines-avoid-c-arrays)
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ActionInfo.v1_4_2.json | 127 …ues for numbers and durations' clause of the Redfish Specification. For arrays, this property sha…
134 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
150 …l appear in the same array order as the `AllowableValues` property. For arrays, this property sha…
163 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
202 …roperty shall contain the maximum value that this service supports. For arrays, this property sha…
212 …roperty shall contain the minimum value that this service supports. For arrays, this property sha…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ActionInfo.v1_4_2.json | 127 …ues for numbers and durations' clause of the Redfish Specification. For arrays, this property sha…
134 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
150 …l appear in the same array order as the `AllowableValues` property. For arrays, this property sha…
163 …lowable values for this parameter as applied to this action target. For arrays, this property sha…
202 …roperty shall contain the maximum value that this service supports. For arrays, this property sha…
212 …roperty shall contain the minimum value that this service supports. For arrays, this property sha…
|
| /openbmc/linux/Documentation/driver-api/md/ |
| H A D | raid5-ppl.rst | 5 Partial Parity Log (PPL) is a feature available for RAID5 arrays. The issue
42 metadata arrays. It can be enabled using mdadm option --consistency-policy=ppl.
45 keep data structures and implementation simple. RAID5 arrays with so many disks
|
| /openbmc/linux/Documentation/translations/sp_SP/process/ |
| H A D | deprecated.rst | 101 <#zero-length-and-one-element-arrays>`_
207 Arrays de longitud variable (VLAs)
209 Usando VLA en la pila (stack) produce un código mucho peor que los arrays
258 Arrays de longitud cero y un elemento
263 en estos casos. El estilo anterior de arrays de un elemento o de longitud
286 para permitir los arrays de longitud cero, para evitar estos tipos de
300 C99 introdujo "los arrays miembros flexibles", los cuales carecen de un
314 los arrays (via sizeof(), `CONFIG_FORTIFY_SOURCE`, y `CONFIG_UBSAN_BOUNDS`).
343 Con respecto a los arrays de un único elemento, se ha de ser consciente de
344 que dichos arrays ocupan al menos tanto espacio como un único objeto del
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-bitarray_3.0.0.bb | 1 SUMMARY = "efficient arrays of booleans -- C extension"
2 DESCRIPTION = "A high-level Python efficient arrays of booleans -- C extension"
|
| /openbmc/qemu/util/ |
| H A D | fdmon-poll.c | 18 * Stack-allocated arrays would be perfect but they have size limitations;
19 * heap allocation is expensive enough that we want to reuse arrays across
21 * any lock, the arrays cannot be stored in AioContext. Thread-local data
|
| /openbmc/linux/Documentation/process/ |
| H A D | deprecated.rst | 95 <#zero-length-and-one-element-arrays>`_ instead.
189 Variable Length Arrays (VLAs)
192 sized stack arrays. While these non-trivial `performance issues
237 Zero-length and one-element arrays
242 for these cases. The older style of one-element or zero-length arrays should
256 was introduced to allow for zero-length arrays, to avoid these kinds of
312 With respect to one-element arrays, one has to be acutely aware that `such arrays
355 existing use of such arrays in those places and the work-around that
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/intel/Protocol/PECI/ |
| H A D | Raw.interface.yaml | 16 An array of byte arrays where each byte array holds the raw
23 An array of byte arrays where each byte array holds the raw
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | generic-radix-tree.rst | 2 Generic radix trees/sparse arrays
6 :doc: Generic radix trees/sparse arrays
|
| /openbmc/linux/drivers/net/ethernet/intel/igc/ |
| H A D | igc_diag.h | 16 /* In the hardware, registers are laid out either singly, in arrays
18 * most tests take place on arrays or single registers (handled
|
| /openbmc/u-boot/include/ |
| H A D | linker_lists.h | 5 * Implementation of linker-generated arrays
41 * generated arrays. The user is expected to build their own macro wrapper
103 * thing: zero-sized arrays, which are both 0-byte-size and exempt from
220 * Since this macro defines the start of the linker-generated arrays,
243 * Since this macro defines the end of the linker-generated arrays,
|
| /openbmc/linux/arch/x86/kernel/ |
| H A D | setup_percpu.c | 176 * initial arrays to the per cpu data areas. These in setup_per_cpu_areas()
177 * arrays then become expendable and the *_early_ptr's in setup_per_cpu_areas()
178 * are zeroed indicating that the static arrays are in setup_per_cpu_areas()
208 /* indicate the early static arrays will soon be gone */ in setup_per_cpu_areas()
|
| /openbmc/linux/net/sched/ |
| H A D | sch_hhf.c | 34 * and k counter arrays. Packets are indexed into k counter arrays by k hash
79 * - F has four counter arrays, each array containing 1024 32-bit counters.
86 * - We need to clear the counter arrays periodically; however, directly
98 #define HHF_ARRAYS_CNT 4 /* number of arrays in multi-stage filter F */
152 * arrays in filter F
258 /* Reset the HHF counter arrays if this is the right time. */ in hhf_classify()
320 /* Conservative update of HHF arrays (see Optimization O2). */ in hhf_classify()
614 /* Initialize heavy-hitter filter arrays. */ in hhf_init()
628 /* Initialize valid bits of heavy-hitter filter arrays. */ in hhf_init()
|
| /openbmc/linux/lib/ |
| H A D | memcat_p.c | 6 * Merge two NULL-terminated pointer arrays into a newly allocated
15 /* count the elements in both arrays */ in __memcat_p()
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z10/ |
| H A D | extended.json | 91 …licDescription": "A translation entry has been written to the Level-2 TLB Page Table Entry arrays."
98 …"A translation entry has been written to the Level-2 TLB Common Region Segment Table Entry arrays."
105 …ry has been written to the Level-2 TLB Common Region Segment Table Entry arrays for a one-megabyte…
|
| /openbmc/linux/arch/loongarch/include/asm/ |
| H A D | uaccess.h | 37 * data types like structures or arrays.
64 * data types like structures or arrays.
89 * data types like structures or arrays.
119 * data types like structures or arrays.
|
| /openbmc/linux/drivers/md/persistent-data/ |
| H A D | dm-array.h | 23 * The arrays implicitly know their length, and bounds are checked for
29 * Arrays are not sparse; if you resize an array to have 'n' entries then
36 * instance data; the same info can be used for many similar arrays if
193 * the cache target needs to iterate both the mapping and hint arrays in
|
| /openbmc/linux/fs/btrfs/ |
| H A D | raid56.h | 98 * These are two arrays of pointers. We allocate the rbio big enough
127 * arrays of sectors, and a lot of IO can use sectors in both arrays.
|