| /openbmc/linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 6 structures (linked_list, rbtree), with particular focus on the verifier's
7 implementation of semantics specific to those data structures.
14 these graph data structures. **No guarantees** of stability for either
24 The BPF map API has historically been the main way to expose data structures
27 interacting with the latter group of data structures can be hard to parse
32 BPF allocator, it is now possible to implement BPF data structures whose API
35 Two such data structures - linked_list and rbtree - have many verification
41 structures.
46 Data structures implemented using the BPF map API have historically used BPF
53 Root and node types for the new data structures are opaquely defined in the
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | magic-number.rst | 8 file, since it is best if the magic numbers used by various structures
11 It is a **very** good idea to protect kernel data structures with magic
15 passing pointers to structures via a void * pointer. The tty code,
17 discipline-specific structures back and forth.
30 structures following the array have been overwritten. Using this
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | boot-time-mm.rst | 7 allocate memory for various data structures, for instance for the
30 Functions and structures
33 Here is the description of memblock data structures, functions and
|
| /openbmc/openbmc/meta-openpower/recipes-bsp/ekb/ |
| H A D | ekb_git.bb | 3 with respective directory structures"
23 # Copying all required hwp's attributes xml file with respective directory structures
|
| /openbmc/linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 12 This document describes RCU's major data structures and their relationship
19 data structures maintain the state in such a way as to allow RCU readers
29 to 16 ``rcu_data`` structures associated with it, so that there are
44 structures.
68 | these structures' ``->structures`` becomes excessive. Experimentation |
124 ``rcu_head`` structures, which are queued on ``rcu_data`` structures
131 structures are related. Lesser data structures will be introduced with
152 The general role of each of these data structures is as follows:
190 and ``rcu_data`` data structures.
836 in the ``rcu_state`` and ``rcu_node`` structures. The
[all …]
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | unshare.rst | 34 requiring additional data structures and mechanisms in the kernel. The
188 appropriate process context structures, populates it with values from
189 the current shared version, associates newly duplicated structures
197 before associating newly duplicated context structures
199 2) unshare() has to allocate and duplicate all context structures
201 current task and releasing older shared structures. Failure
214 appropriate context structures and then associate them with the
229 4) Appropriately release older, shared, context structures.
256 duplicated structures to the task structure with which the
272 * If any new structures are created by unshare_* helper
[all …]
|
| /openbmc/qemu/tests/avocado/acpi-bits/bits-config/ |
| H A D | bits-cfg.txt | 9 # acpi: Dump all ACPI structures.
10 # smbios: Dump all SMBIOS structures.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libtest/ |
| H A D | libtest-deep-perl_1.204.bb | 7 the result you were expecting. At its simplest it compares two structures \
10 correct class. It also handles circular data structures without getting \
18 instead. Test::Deep provides pattern matching for complex data structures \
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2-mplane.rst | 4 Multi-planar format structures
7 The struct :c:type:`v4l2_plane_pix_format` structures define size
11 array of struct :c:type:`v4l2_plane_pix_format` structures,
86 - An array of structures describing format of each plane this pixel
|
| H A D | planar-apis.rst | 19 Some of the V4L2 API calls and structures are interpreted differently,
35 in multi-planar API structures), while the single-planar API cannot
48 New structures for describing multi-planar formats are added: struct
|
| /openbmc/qemu/hw/acpi/ |
| H A D | nvdimm.c | 209 nvdimm_build_structure_spa(GArray *structures, DeviceState *dev) in nvdimm_build_structure_spa() argument
221 nfit_spa = acpi_data_push(structures, sizeof(*nfit_spa)); in nvdimm_build_structure_spa()
257 nvdimm_build_structure_memdev(GArray *structures, DeviceState *dev) in nvdimm_build_structure_memdev() argument
267 nfit_memdev = acpi_data_push(structures, sizeof(*nfit_memdev)); in nvdimm_build_structure_memdev()
305 nfit_dcr = acpi_data_push(structures, sizeof(*nfit_dcr)); in nvdimm_build_structure_dcr()
333 nfit_caps = acpi_data_push(structures, sizeof(*nfit_caps)); in nvdimm_build_structure_caps()
344 GArray *structures = g_array_new(false, true /* clear */, 1); in nvdimm_build_device_structure() local
350 nvdimm_build_structure_spa(structures, dev); in nvdimm_build_device_structure()
356 nvdimm_build_structure_memdev(structures, dev); in nvdimm_build_device_structure()
359 nvdimm_build_structure_dcr(structures, dev); in nvdimm_build_device_structure()
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-dmi-tables | 5 The firmware provides DMI structures as a packed list of
10 The format of SMBIOS entry point and DMI structures
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | persistent-data.rst | 10 different targets were rolling their own data structures, for example:
17 Maintaining these data structures takes a lot of work, so if possible
62 On-disk data structures that keep track of reference counts of blocks.
69 The data structures
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 121.out | 3 === New refcount structures may not conflict with existing structures ===
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/uthash/ |
| H A D | uthash_2.3.0.bb | 1 SUMMARY = "Hash table and linked list for C structures"
4 * utlist.h provides linked list macros for C structures\n\
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | ioctl.rst | 55 Some subsystems use version numbers in data structures to overload
89 incompatible definitions of these structures in user space after the
93 in other data structures when separate second/nanosecond values are
119 As long as all the rules for data structures are followed, this is as
141 are pointers to compatible data structures.
146 Compatible data structures have the same layout on all architectures,
151 data structures. Fixed-length replacements are ``__s32``, ``__u32``,
174 To avoid this problem, all structures should have their members
179 * On ARM OABI user space, structures are padded to multiples of 32-bit,
203 implicit padding in data structures. Where there is implicit padding
|
| /openbmc/linux/Documentation/driver-api/tty/ |
| H A D | index.rst | 10 TTY structures
13 There are several major TTY structures. Every TTY device in a system has a
29 In-detail description of the named TTY structures is in separate documents:
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | vga-switcheroo.rst | 34 Public structures
55 Private structures
|
| /openbmc/linux/Documentation/devicetree/bindings/firmware/ |
| H A D | coreboot.txt | 4 bookkeeping structures to the kernel. Since coreboot itself cannot boot a
18 coreboot to dynamically allocate data structures that remain resident.
|
| /openbmc/openbmc/poky/meta/recipes-extended/libarchive/libarchive/ |
| H A D | configurehack.patch | 14 +# Checks for typedefs, structures, and compiler characteristics.
34 -# Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | checksums.rst | 7 and jbd2 data structures. The associated feature flag is metadata_csum.
10 structures did not have space to fit a full 32-bit checksum, so only the
13 structures. However, existing 32-bit filesystems cannot be extended to
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/pidgin/pidgin-sipe/ |
| H A D | 0001-Align-structs-casts-with-time_t-elements-to-8byte-bo.patch | 7 structures are typcasted to another struct types which have time_t
8 element, that now increases the natural alignment boundary of structures
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/core/ |
| H A D | 0004-adb-Fix-build-on-big-endian-systems.patch | 8 when initializing structures, i.e in a context where a function call
17 them to be used when initializing structures.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/selinux/recipes-devtool/android-tools/android-tools/ |
| H A D | 0004-adb-Fix-build-on-big-endian-systems.patch | 8 when initializing structures, i.e in a context where a function call
17 them to be used when initializing structures.
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | v4l2-tveeprom.rst | 3 Hauppauge TV EEPROM functions and data structures
|