| /openbmc/linux/arch/arm/nwfpe/ |
| H A D | ChangeLog | 35 * fpa11.h - modified FPA11, FPREG structures
51 over one of the most important structures in the entire OS.
63 structures, and that recycled ones may not have init_flag zeroed.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/libgee/ |
| H A D | libgee_0.20.6.bb | 2 and classes for commonly used data structures."
|
| /openbmc/linux/Documentation/mm/ |
| H A D | physical_memory.rst | 9 chapter describes the structures used to manage physical memory in a running
26 For NUMA architectures, the node structures are allocated by the architecture
27 specific code early during boot. Usually, these structures are allocated
150 structures. The actual structures are allocated early during boot when
157 Along with the node structures, kernel maintains an array of ``nodemask_t``
220 core memory management structures.
|
| /openbmc/u-boot/drivers/block/ |
| H A D | Kconfig | 49 it will prevent repeated reads from directory structures and other
50 filesystem data structures.
|
| /openbmc/phosphor-fan-presence/docs/control/ |
| H A D | debug.md | 3 Fan control's internal data structures can be dumped at runtime using the
4 `fanctl dump` command, which triggers fan control to write the structures to a
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pytest-lazy-fixtures_1.0.7.bb | 8 * You can use fixtures in any data structures\
|
| H A D | python3-pyasn1-modules_0.4.0.bb | 4 data structures (X.509, PKCS etc.)."
|
| H A D | python3-uefi-firmware_1.11.bb | 1 SUMMARY = "Various data structures and parsing tools for UEFI firmware."
|
| H A D | python3-pandas_2.0.3.bb | 3 high-performance, easy-to-use data structures and data analysis tools for \
|
| /openbmc/linux/Documentation/locking/ |
| H A D | pi-futex.rst | 35 lockless structures are rather the exception than the norm - the current
36 ratio of lockless vs. locky code for shared data structures is somewhere
39 I.e. critical RT apps often choose lock structures to protect critical
40 data structures, instead of lockless algorithms. Furthermore, there are
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | shadow-vars.rst | 6 additional "shadow" data with existing data structures. Shadow data is
7 allocated separately from parent data structures, which are left
110 If parent data structures are frequently created and destroyed, it may
226 a datatype update technique called "shadow data structures".
|
| /openbmc/linux/Documentation/driver-api/80211/ |
| H A D | introduction.rst | 12 structures and functions used in the kernel as well as giving a
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/rp-pppoe/rp-pppoe/ |
| H A D | 0002-Enable-support-for-the-kernel-module.patch | 25 dnl Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/linux/drivers/firmware/google/ |
| H A D | Kconfig | 27 Coreboot BIOS containing tagged data structures from the
28 BIOS. These data structures expose things like the verified
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | s390-drivers.rst | 62 Some hardware structures have been translated into C structures for use
64 hardware structures represented here, please consult the Principles of
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libnvme/ |
| H A D | libnvme_1.8.bb | 3 libnvme provides type definitions for NVMe specification structures, \
|
| /openbmc/linux/Documentation/w1/ |
| H A D | w1-netlink.rst | 68 For event messages there are no w1_netlink_cmd embedded structures,
149 structures.
158 w1_netlink_msg, if there are no w1_netlink_cmd structures,
161 All w1_netlink_cmd command structures are handled in every w1_netlink_msg,
|
| /openbmc/openbmc/poky/meta/recipes-extended/tcp-wrappers/tcp-wrappers-7.6/ |
| H A D | siglongjmp.patch | 23 /* rfc931 - return remote user name, given socket structures */
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mysql-python/ |
| H A D | 0001-_mysql.c-fix-compilation-with-MariaDB-with-10.3.13.patch | 7 instead of direct modification of internal structures
|
| /openbmc/linux/Documentation/security/ |
| H A D | lsm-development.rst | 14 see ``security/security.c`` and associated structures:
|
| H A D | self-protection.rst | 6 structures within the Linux kernel to protect against security flaws in
75 tables, file/network/etc operation structures, etc). The number of these
145 There are many memory structures in the kernel that are regularly abused
167 the kernel's preallocated stack space and into sensitive structures. Two
175 The structures used to track heap free lists can be sanity-checked during
259 structures, attacks must either be tuned to known kernel builds or expose
267 Since the locations of sensitive structures are the primary target for
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | highuid.rst | 12 - kernel code should use uid_t and gid_t in kernel-private structures and
69 more are needed. (as well as new user<->kernel data structures)
|
| /openbmc/linux/Documentation/driver-api/pldmfw/ |
| H A D | index.rst | 29 firmware file into data structures, and then uses the provided function
46 library parses and extracts this data into simpler structures for ease of
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yasm/yasm/ |
| H A D | 0001-Do-not-use-AC_HEADER_STDC.patch | 35 # Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/linux/Documentation/gpu/rfc/ |
| H A D | index.rst | 13 * For uapi structures add a file to this directory with and then pull the
|