Home
last modified time | relevance | path

Searched full:hierarchies (Results 1 – 25 of 26) sorted by relevance

12

/openbmc/openbmc/meta-openembedded/meta-python/recipes/devtool/
H A Dpython3-exhale_0.3.7.bb4 Exhale revives Doxygen's class, file, and page hierarchies in reStructuredText documents \
5 to make these hierarchies available in Sphinx documented projects."
/openbmc/docs/designs/
H A Dphysical-topology.md22 path hierarchies (Proposal I).
153 ### Path hierarchies
164 A potential compromise would be allowing a combination of path hierarchies and
170 with this method. If the additional complexity of path hierarchies is needed in
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/php/php/
H A Dphp-fpm.service40 # The Linux Control Groups (cgroups(7)) hierarchies accessible through /sys/fs/cgroup will be
42 # require write access to the control groups hierarchies; it is hence recommended to turn this on
/openbmc/u-boot/test/py/tests/
H A Dtest_tpm2.py93 Use the LOCKOUT hierarchy for this. The LOCKOUT/PLATFORM hierarchies must
95 PLATFORM hierarchies are also available.
112 Use the LOCKOUT hierarchy for this. ENDORSEMENT and PLATFORM hierarchies are
/openbmc/qemu/docs/
H A Dpcie.txt33 The recommendation is to separate the PCI Express and PCI hierarchies.
52 PCI Express hierarchies.
55 hierarchies.
79 Always use PCI Express Root Ports to start PCI Express hierarchies.
139 combination with PCI-PCI Bridges (pci-bridge) to start PCI hierarchies.
141 Prefer flat hierarchies. For most scenarios a single PCI Express to PCI Bridge
H A Dpcie_pci_bridge.txt7 hierarchies creation on Q35 machines.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/Threshold/
H A DSoftShutdown.interface.yaml4 hierarchy within the sensors namespace. The following sensor hierarchies
H A DPerformanceLoss.interface.yaml5 hierarchies are recognized:
H A DHardShutdown.interface.yaml6 hierarchies are recognized:
H A DWarning.interface.yaml4 within the sensors namespace. The following sensor hierarchies are
H A DCritical.interface.yaml4 within the sensors namespace. The following sensor hierarchies are
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/
H A DValue.interface.yaml4 namespace. The following sensor hierarchies are recognized:
/openbmc/linux/Documentation/admin-guide/hw-vuln/
Dcore-scheduling.rst
/openbmc/phosphor-dbus-interfaces/
H A Drequirements.md59 required to be represented in different dbus path hierarchies due to some
/openbmc/linux/Documentation/filesystems/
Dsysfs.rst
/openbmc/linux/Documentation/driver-api/pci/
Dp2pdma.rst
/openbmc/u-boot/drivers/tpm/
H A Dtpm2_tis_sandbox.c14 /* Hierarchies */
/openbmc/linux/Documentation/core-api/
Dkobject.rst
/openbmc/qemu/docs/devel/
H A Dmulti-process.rst306 in the same place in the object and bus hierarchies as the objects they
/openbmc/openbmc/poky/meta/recipes-devtools/syslinux/syslinux/
H A D0001-ext2_fs.h-do-not-carry-an-outdated-copy.patch640 -#define EXT2_TOPDIR_FL 0x00020000 /* Top of directory hierarchies*/
/openbmc/linux/tools/testing/selftests/landlock/
Dfs_test.c
/openbmc/linux/Documentation/RCU/
DRTFP.txt
/openbmc/qemu/target/riscv/
H A Dcpu.c2765 * Hack to simplify CPU class hierarchies that include both 32- and in riscv_cpu_class_base_init()
/openbmc/openbmc/poky/documentation/overview-manual/
H A Dconcepts.rst754 In the previous figure, notice that there are two sample hierarchies:
/openbmc/qemu/
H A Dqemu-options.hx5120 superscalar out of order cores with complex cache hierarchies. The

12