| /openbmc/docs/designs/ |
| H A D | physical-topology.md | 22 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/linux/Documentation/userspace-api/ |
| H A D | landlock.rst | 186 Following this good practice leads to self-sufficient hierarchies that do not
193 Having self-sufficient hierarchies also helps to tighten the required access
219 Landlock enables to restrict access to file hierarchies, which means that these
228 access to multiple file hierarchies at the same time, whether these hierarchies
235 policy point of view, each OverlayFS layers and merge hierarchies are
239 then only think about file hierarchies they want to allow access to, regardless
405 hierarchies. Future Landlock evolutions could still enable to explicitly
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/php/php/ |
| H A D | php-fpm.service | 40 # 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 D | test_tpm2.py | 93 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 D | pcie.txt | 33 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 D | pcie_pci_bridge.txt | 7 hierarchies creation on Q35 machines.
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cgroups.rst | 30 2.3 Mounting hierarchies by name
66 At any one time there may be multiple active hierarchies of task
103 different subsystems - having parallel hierarchies allows each
114 that can benefit from multiple hierarchies, consider a large
143 (by putting those resource subsystems in different hierarchies),
366 different hierarchies of cgroups for each single resource or group of
473 2.3 Mounting hierarchies by name
|
| H A D | pids.rst | 34 pids.current tracks all child cgroup hierarchies, so parent/pids.current is a
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | cgroup-v2.rst | 86 R-1. Multiple Hierarchies
152 bound to other hierarchies. This allows mixing v2 hierarchy with the
153 legacy v1 multiple hierarchies in a fully backward compatible way.
155 A controller can be moved across hierarchies only after the controller
162 controller to become available for other hierarchies; furthermore, due
167 controllers dynamically between the v2 and other hierarchies is
169 the hierarchies and controller associations before starting using the
2581 legacy hierarchies, this may be unexpected.
2731 - Multiple hierarchies including named ones are not supported.
2746 Multiple Hierarchies
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/Threshold/ |
| H A D | HardShutdown.interface.yaml | 6 hierarchies are recognized:
|
| H A D | Warning.interface.yaml | 4 within the sensors namespace. The following sensor hierarchies are
|
| H A D | SoftShutdown.interface.yaml | 4 hierarchy within the sensors namespace. The following sensor hierarchies
|
| H A D | Critical.interface.yaml | 4 within the sensors namespace. The following sensor hierarchies are
|
| H A D | PerformanceLoss.interface.yaml | 5 hierarchies are recognized:
|
| /openbmc/linux/kernel/cgroup/ |
| H A D | cgroup-internal.h | 88 * belong to different cgroups on different hierarchies. In the other
171 /* iterate across the hierarchies */
|
| H A D | cgroup-v1.c | 621 /* cgroup core interface files for the legacy hierarchies */
1049 * empty hierarchies must have a name). in check_cgroupfs_options()
1100 /* remounting is not allowed for populated hierarchies */ in cgroup1_reconfigure()
1207 * specification is allowed for already existing hierarchies but we in cgroup1_root_to_use()
1213 /* Hierarchies may only be created in the initial cgroup namespace. */ in cgroup1_root_to_use()
|
| H A D | pids.c | 25 * pids.current tracks all child cgroup hierarchies, so parent/pids.current is
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/ |
| H A D | Value.interface.yaml | 4 namespace. The following sensor hierarchies are recognized:
|
| /openbmc/linux/include/linux/ |
| H A D | cgroup-defs.h | 546 /* A list running through the active hierarchies */
705 * hierarchies coexisting with csses for the current one.
745 struct cftype *legacy_cftypes; /* for the legacy hierarchies */
801 * On legacy hierarchies, net_prio and net_cls controllers directly
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 77 Building hierarchies of tasks
79 The simplest way to build hierarchies of threads/processes which share a
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | requirements.md | 59 required to be represented in different dbus path hierarchies due to some
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | sysfs.rst | 41 of the kobject's parent, expressing internal object hierarchies to
43 ancestors of object hierarchies; i.e. the subsystems the objects
|
| /openbmc/linux/Documentation/driver-api/pci/ |
| H A D | p2pdma.rst | 21 between hierarchies.
|
| /openbmc/linux/tools/include/uapi/linux/ |
| H A D | fs.h | 259 #define FS_TOPDIR_FL 0x00020000 /* Top of directory hierarchies*/
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | fs.h | 259 #define FS_TOPDIR_FL 0x00020000 /* Top of directory hierarchies*/
|