| /Linux-v5.15/Documentation/admin-guide/media/ |
| D | dvb_intro.rst | 153 HIERARCHY = NONE
181 HIERARCHY = NONE
196 HIERARCHY = NONE
211 HIERARCHY = NONE
226 HIERARCHY = NONE
241 HIERARCHY = NONE
256 HIERARCHY = NONE
271 HIERARCHY = NONE
286 HIERARCHY = NONE
301 HIERARCHY = NONE
[all …]
|
| /Linux-v5.15/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 60 A *hierarchy* is a set of cgroups arranged in a tree, such that
62 hierarchy, and a set of subsystems; each subsystem has system-specific
63 state attached to each cgroup in the hierarchy. Each hierarchy has
67 cgroups. Each hierarchy is a partition of all tasks in the system.
72 a cgroup. Those creations and assignments only affect the hierarchy
99 Multiple hierarchy support is provided to allow for situations where
102 hierarchy to be a natural division of tasks, without having to handle
108 separate hierarchy; at the other extreme, all subsystems
109 would be attached to the same hierarchy.
147 With only a single hierarchy, he now would potentially have to create
[all …]
|
| D | pids.rst | 8 The process number controller is used to allow a cgroup hierarchy to stop any
13 preventable in the scope of a cgroup hierarchy by allowing resource limiting of
32 limit in the hierarchy is followed).
49 Then we create a hierarchy, set limits and attach processes to it::
68 not be able to overcome the most stringent limit in the hierarchy (in this case,
|
| D | devices.rst | 57 4. Hierarchy
60 device cgroups maintain hierarchy by making sure a cgroup never has more
123 4.1 Hierarchy (internal implementation)
130 to devices will be propagated down the hierarchy.
|
| /Linux-v5.15/security/landlock/ |
| D | ruleset.c | 40 * hierarchy = NULL in create_ruleset()
243 static inline void get_hierarchy(struct landlock_hierarchy *const hierarchy) in get_hierarchy() argument
245 if (hierarchy) in get_hierarchy()
246 refcount_inc(&hierarchy->usage); in get_hierarchy()
249 static void put_hierarchy(struct landlock_hierarchy *hierarchy) in put_hierarchy() argument
251 while (hierarchy && refcount_dec_and_test(&hierarchy->usage)) { in put_hierarchy()
252 const struct landlock_hierarchy *const freeme = hierarchy; in put_hierarchy()
254 hierarchy = hierarchy->parent; in put_hierarchy()
270 if (WARN_ON_ONCE(!dst || !dst->hierarchy)) in merge_ruleset()
343 if (WARN_ON_ONCE(!parent->hierarchy)) { in inherit_ruleset()
[all …]
|
| D | ruleset.h | 61 * struct landlock_hierarchy - Node in a ruleset hierarchy
90 * @hierarchy: Enables hierarchy identification even when a parent
93 struct landlock_hierarchy *hierarchy; member
|
| D | ptrace.c | 41 for (walker = child->hierarchy; walker; walker = walker->parent) { in domain_scope_le()
42 if (walker == parent->hierarchy) in domain_scope_le()
43 /* @parent is in the scoped hierarchy of @child. */ in domain_scope_le()
|
| /Linux-v5.15/Documentation/core-api/irq/ |
| D | irq-domain.rst | 218 Hierarchy IRQ domain
235 interrupt controller and those irq_domains are organized into hierarchy.
236 When building irq_domain hierarchy, the irq_domain near to the device is
237 child and the irq_domain near to CPU is parent. So a hierarchy structure
248 There are four major interfaces to use hierarchy irq_domain:
259 Following changes are needed to support hierarchy irq_domain:
262 maintain irq_domain hierarchy information.
264 build hierarchy irq_data to match hierarchy irq_domains. The irq_data
266 3) new callbacks are added to struct irq_domain_ops to support hierarchy
269 With support of hierarchy irq_domain and hierarchy irq_data ready, an
[all …]
|
| /Linux-v5.15/drivers/media/dvb-frontends/ |
| D | as102_fe.c | 125 switch (c->hierarchy) { in as102_fe_set_frontend()
127 tune_args.hierarchy = HIER_NONE; in as102_fe_set_frontend()
130 tune_args.hierarchy = HIER_ALPHA_1; in as102_fe_set_frontend()
133 tune_args.hierarchy = HIER_ALPHA_2; in as102_fe_set_frontend()
136 tune_args.hierarchy = HIER_ALPHA_4; in as102_fe_set_frontend()
139 tune_args.hierarchy = HIER_UNKNOWN; in as102_fe_set_frontend()
149 * Detect a hierarchy selection in as102_fe_set_frontend()
152 if ((tune_args.hierarchy != HIER_NONE) && in as102_fe_set_frontend()
169 tune_args.hierarchy, in as102_fe_set_frontend()
209 /* extract hierarchy */ in as102_fe_get_frontend()
[all …]
|
| D | as102_fe_types.h | 19 /* hierarchy priority selection values */
30 /* hierarchy available values */
101 uint8_t hierarchy; member
117 /* hierarchy selection */
121 /* hierarchy */
122 uint8_t hierarchy; member
|
| D | dib3000mb.c | 224 switch (c->hierarchy) { in dib3000mb_set_frontend()
226 deb_setf("hierarchy: none\n"); in dib3000mb_set_frontend()
229 deb_setf("hierarchy: alpha=1\n"); in dib3000mb_set_frontend()
233 deb_setf("hierarchy: alpha=2\n"); in dib3000mb_set_frontend()
237 deb_setf("hierarchy: alpha=4\n"); in dib3000mb_set_frontend()
241 deb_setf("hierarchy: alpha=auto\n"); in dib3000mb_set_frontend()
247 if (c->hierarchy == HIERARCHY_NONE) { in dib3000mb_set_frontend()
251 } else if (c->hierarchy != HIERARCHY_AUTO) { in dib3000mb_set_frontend()
328 c->hierarchy == HIERARCHY_AUTO || in dib3000mb_set_frontend()
504 c->hierarchy = HIERARCHY_NONE; in dib3000mb_get_frontend()
[all …]
|
| D | l64781.c | 157 if (p->hierarchy != HIERARCHY_NONE && in apply_frontend_param()
175 if ((int)p->hierarchy < HIERARCHY_NONE || in apply_frontend_param()
176 p->hierarchy > HIERARCHY_4) in apply_frontend_param()
200 if (p->hierarchy != HIERARCHY_NONE) in apply_frontend_param()
203 val0x06 = (p->hierarchy << 2) | p->modulation; in apply_frontend_param()
323 p->hierarchy = HIERARCHY_NONE; in get_frontend()
326 p->hierarchy = HIERARCHY_1; in get_frontend()
329 p->hierarchy = HIERARCHY_2; in get_frontend()
332 p->hierarchy = HIERARCHY_4; in get_frontend()
335 printk("Unexpected value for hierarchy\n"); in get_frontend()
|
| D | stv0367_priv.h | 103 FE_TER_HIER_NONE, /*Hierarchy None*/
104 FE_TER_HIER_LOW_PRIO, /*Hierarchy : Low Priority*/
105 FE_TER_HIER_HIGH_PRIO, /*Hierarchy : High Priority*/
106 FE_TER_HIER_PRIO_ANY /*Hierarchy :Any*/
|
| D | mt352.c | 201 if (op->hierarchy == HIERARCHY_AUTO || in mt352_set_parameters()
202 op->hierarchy == HIERARCHY_NONE) in mt352_set_parameters()
251 switch (op->hierarchy) { in mt352_set_parameters()
373 op->hierarchy = HIERARCHY_NONE; in mt352_get_parameters()
376 op->hierarchy = HIERARCHY_1; in mt352_get_parameters()
379 op->hierarchy = HIERARCHY_2; in mt352_get_parameters()
382 op->hierarchy = HIERARCHY_4; in mt352_get_parameters()
385 op->hierarchy = HIERARCHY_AUTO; in mt352_get_parameters()
|
| D | zl10353.c | 258 if (c->hierarchy == HIERARCHY_AUTO || in zl10353_set_parameters()
259 c->hierarchy == HIERARCHY_NONE) in zl10353_set_parameters()
308 switch (c->hierarchy) { in zl10353_set_parameters()
427 c->hierarchy = HIERARCHY_NONE; in zl10353_get_parameters()
430 c->hierarchy = HIERARCHY_1; in zl10353_get_parameters()
433 c->hierarchy = HIERARCHY_2; in zl10353_get_parameters()
436 c->hierarchy = HIERARCHY_4; in zl10353_get_parameters()
439 c->hierarchy = HIERARCHY_AUTO; in zl10353_get_parameters()
|
| /Linux-v5.15/tools/testing/selftests/landlock/ |
| D | ptrace_test.c | 62 FIXTURE(hierarchy) { }; in FIXTURE() argument
64 FIXTURE_VARIANT(hierarchy) { in FIXTURE_VARIANT() argument
86 FIXTURE_VARIANT_ADD(hierarchy, allow_without_domain) { in FIXTURE_VARIANT_ADD() argument
101 FIXTURE_VARIANT_ADD(hierarchy, allow_with_one_domain) { in FIXTURE_VARIANT_ADD() argument
115 FIXTURE_VARIANT_ADD(hierarchy, deny_with_parent_domain) { in FIXTURE_VARIANT_ADD() argument
130 FIXTURE_VARIANT_ADD(hierarchy, deny_with_sibling_domain) { in FIXTURE_VARIANT_ADD() argument
145 FIXTURE_VARIANT_ADD(hierarchy, allow_sibling_domain) { in FIXTURE_VARIANT_ADD() argument
161 FIXTURE_VARIANT_ADD(hierarchy, allow_with_nested_domain) { in FIXTURE_VARIANT_ADD() argument
177 FIXTURE_VARIANT_ADD(hierarchy, deny_with_nested_and_parent_domain) { in FIXTURE_VARIANT_ADD() argument
195 FIXTURE_VARIANT_ADD(hierarchy, deny_with_forked_domain) { in FIXTURE_VARIANT_ADD() argument
[all …]
|
| /Linux-v5.15/include/linux/ |
| D | cgroup-defs.h | 119 __CFTYPE_ONLY_ON_DFL = (1 << 16), /* only on default hierarchy */
120 __CFTYPE_NOT_ON_DFL = (1 << 17), /* not on default hierarchy */
239 * On the default hierarchy, ->subsys[ssid] may point to a css
295 * hierarchy on reads.
368 * step down the hierarchy increments the level. This along with
370 * descendant of another without traversing the hierarchy.
437 * On the default hierarchy, a css_set for a cgroup with some
494 * A cgroup_root represents the root of a cgroup hierarchy, and may be
495 * associated with a kernfs_root to form an active hierarchy. This is
501 /* The bitmask of subsystems attached to this hierarchy */
[all …]
|
| /Linux-v5.15/fs/9p/ |
| D | v9fs.h | 17 * @V9FS_ACCESS_SINGLE: only the mounting user can access the hierarchy
67 * @uname: string user name to mount hierarchy as
68 * @aname: mount specifier for remote hierarchy
70 * @dfltuid: default numeric userid to mount hierarchy as
71 * @dfltgid: default numeric groupid to mount hierarchy as
72 * @uid: if %V9FS_ACCESS_SINGLE, the numeric uid which mounted the hierarchy
96 char *aname; /* name of remote hierarchy being mounted */
|
| /Linux-v5.15/Documentation/userspace-api/ |
| D | landlock.rst | 25 file hierarchy, and the related filesystem actions are defined with `access
65 file hierarchy ``/usr``. Without another rule, write actions would then be
151 A bind mount mirrors a source file hierarchy to a destination. The destination
152 hierarchy is then composed of the exact same files, on which Landlock rules can
159 combined in a merge directory, result of the mount point. This merge hierarchy
161 on the merge hierarchy only reflects on the upper layer. From a Landlock
165 restrict the resulted merged hierarchy, and vice versa. Landlock users should
238 to its hierarchy. Because files are identified and restricted by their
239 hierarchy, moving or linking a file from one directory to another implies to
240 propagate the hierarchy constraints. To protect against privilege escalations
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 110 distribute system resources along the hierarchy in a controlled and
116 distributing a specific type of system resource along the hierarchy
131 sub-hierarchy of the cgroup. When a controller is enabled on a nested
133 restrictions set closer to the root in the hierarchy can not be
143 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
144 hierarchy can be mounted with the following mount command::
149 controllers which support v2 and are not bound to a v1 hierarchy are
150 automatically bound to the v2 hierarchy and show up at the root.
151 Controllers which are not in active use in the v2 hierarchy can be
152 bound to other hierarchies. This allows mixing v2 hierarchy with the
[all …]
|
| /Linux-v5.15/drivers/edac/ |
| D | debugfs.c | 82 /* Create a toplevel dir under EDAC's debugfs hierarchy */
92 /* Create a toplevel dir under EDAC's debugfs hierarchy with parent @parent */
101 * Create a file under EDAC's hierarchy or a sub-hierarchy:
|
| /Linux-v5.15/drivers/usb/gadget/function/ |
| D | uvc_configfs.c | 151 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
175 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
270 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
304 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_default_processing_bm_controls_show()
373 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
415 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_default_camera_bm_controls_show()
487 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
599 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_control_class_allow_link()
640 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_control_class_drop_link()
725 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_default_control_b_interface_number_show()
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.yaml | 36 This node contains a hierarchy of PM domain nodes, which should match the
37 Power Area Hierarchy in the Power Domain Specifications section of the
90 // This shows a subset of the r8a7740 PM domain hierarchy, containing the
|
| /Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | rl.c | 39 int mlx5_create_scheduling_element_cmd(struct mlx5_core_dev *dev, u8 hierarchy, in mlx5_create_scheduling_element_cmd() argument
52 hierarchy); in mlx5_create_scheduling_element_cmd()
64 int mlx5_modify_scheduling_element_cmd(struct mlx5_core_dev *dev, u8 hierarchy, in mlx5_modify_scheduling_element_cmd() argument
80 hierarchy); in mlx5_modify_scheduling_element_cmd()
86 int mlx5_destroy_scheduling_element_cmd(struct mlx5_core_dev *dev, u8 hierarchy, in mlx5_destroy_scheduling_element_cmd() argument
96 hierarchy); in mlx5_destroy_scheduling_element_cmd()
|
| /Linux-v5.15/Documentation/driver-api/pci/ |
| D | p2pdma.rst | 13 transactions between hierarchy domains, and in PCIe, each Root Port
14 defines a separate hierarchy domain. To make things worse, there is no
18 same PCI bridge, as such devices are all in the same PCI hierarchy
20 hierarchy will be routable, but it does not require routing
|
