| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-6.6/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
101 Multiple hierarchy support is provided to allow for situations where
104 hierarchy to be a natural division of tasks, without having to handle
110 separate hierarchy; at the other extreme, all subsystems
111 would be attached to the same hierarchy.
149 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,
|
| /kernel/linux/linux-6.6/drivers/powercap/ |
| D | dtpm.c | 330 * dtpm_unregister - Unregister a dtpm node from the hierarchy tree
344 * dtpm_register - Register a dtpm node in the hierarchy tree
350 * is the root node of the hierarchy. If the root node already exists,
415 static struct dtpm *dtpm_setup_virtual(const struct dtpm_node *hierarchy, in dtpm_setup_virtual() argument
426 ret = dtpm_register(hierarchy->name, dtpm, parent); in dtpm_setup_virtual()
429 hierarchy->name, ret); in dtpm_setup_virtual()
437 static struct dtpm *dtpm_setup_dt(const struct dtpm_node *hierarchy, in dtpm_setup_dt() argument
443 np = of_find_node_by_path(hierarchy->name); in dtpm_setup_dt()
445 pr_err("Failed to find '%s'\n", hierarchy->name); in dtpm_setup_dt()
478 static int dtpm_for_each_child(const struct dtpm_node *hierarchy, in dtpm_for_each_child() argument
[all …]
|
| /kernel/linux/linux-6.6/security/landlock/ |
| D | ruleset.c | 41 * hierarchy = NULL in create_ruleset()
245 static inline void get_hierarchy(struct landlock_hierarchy *const hierarchy) in get_hierarchy() argument
247 if (hierarchy) in get_hierarchy()
248 refcount_inc(&hierarchy->usage); in get_hierarchy()
251 static void put_hierarchy(struct landlock_hierarchy *hierarchy) in put_hierarchy() argument
253 while (hierarchy && refcount_dec_and_test(&hierarchy->usage)) { in put_hierarchy()
254 const struct landlock_hierarchy *const freeme = hierarchy; in put_hierarchy()
256 hierarchy = hierarchy->parent; in put_hierarchy()
272 if (WARN_ON_ONCE(!dst || !dst->hierarchy)) in merge_ruleset()
346 if (WARN_ON_ONCE(!parent->hierarchy)) { in inherit_ruleset()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/irq/ |
| D | irq-domain.rst | 188 Hierarchy IRQ domain
205 interrupt controller and those irq_domains are organized into hierarchy.
206 When building irq_domain hierarchy, the irq_domain near to the device is
207 child and the irq_domain near to CPU is parent. So a hierarchy structure
218 There are four major interfaces to use hierarchy irq_domain:
229 Following changes are needed to support hierarchy irq_domain:
232 maintain irq_domain hierarchy information.
234 build hierarchy irq_data to match hierarchy irq_domains. The irq_data
236 3) new callbacks are added to struct irq_domain_ops to support hierarchy
239 With support of hierarchy irq_domain and hierarchy irq_data ready, an
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/irq/ |
| D | irq-domain.rst | 215 Hierarchy IRQ domain
232 interrupt controller and those irq_domains are organized into hierarchy.
233 When building irq_domain hierarchy, the irq_domain near to the device is
234 child and the irq_domain near to CPU is parent. So a hierarchy structure
245 There are four major interfaces to use hierarchy irq_domain:
256 Following changes are needed to support hierarchy irq_domain:
259 maintain irq_domain hierarchy information.
261 build hierarchy irq_data to match hierarchy irq_domains. The irq_data
263 3) new callbacks are added to struct irq_domain_ops to support hierarchy
266 With support of hierarchy irq_domain and hierarchy irq_data ready, an
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | page_tables.rst | 16 Linux defines page tables as a hierarchy which is currently five levels in
38 Over time a deeper hierarchy has been developed in response to increasing memory
44 The software page table hierarchy reflects the fact that page table hardware has
53 to mark large areas as unmapped at a higher level in the page table hierarchy.
59 traverse deeper in the hierarchy when you find a large mapped range like this.
61 The page table hierarchy has now developed into this::
84 Symbols on the different levels of the page table hierarchy have the following
102 - **pmd**, `pmd_t`, `pmdval_t` = **Page Middle Directory**, the hierarchy right
124 To repeat: each level in the page table hierarchy is a *array of pointers*, so
|
| /kernel/linux/linux-6.6/tools/testing/selftests/landlock/ |
| D | ptrace_test.c | 89 FIXTURE(hierarchy) {}; in FIXTURE() argument
92 FIXTURE_VARIANT(hierarchy) in FIXTURE_VARIANT() argument
116 FIXTURE_VARIANT_ADD(hierarchy, allow_without_domain) { in FIXTURE_VARIANT_ADD() argument
133 FIXTURE_VARIANT_ADD(hierarchy, allow_with_one_domain) { in FIXTURE_VARIANT_ADD() argument
149 FIXTURE_VARIANT_ADD(hierarchy, deny_with_parent_domain) { in FIXTURE_VARIANT_ADD() argument
166 FIXTURE_VARIANT_ADD(hierarchy, deny_with_sibling_domain) { in FIXTURE_VARIANT_ADD() argument
183 FIXTURE_VARIANT_ADD(hierarchy, allow_sibling_domain) { in FIXTURE_VARIANT_ADD() argument
201 FIXTURE_VARIANT_ADD(hierarchy, allow_with_nested_domain) { in FIXTURE_VARIANT_ADD() argument
219 FIXTURE_VARIANT_ADD(hierarchy, deny_with_nested_and_parent_domain) { in FIXTURE_VARIANT_ADD() argument
239 FIXTURE_VARIANT_ADD(hierarchy, deny_with_forked_domain) { in FIXTURE_VARIANT_ADD() argument
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cgroup-defs.h | 115 __CFTYPE_ONLY_ON_DFL = (1 << 16), /* only on default hierarchy */
116 __CFTYPE_NOT_ON_DFL = (1 << 17), /* not on default hierarchy */
292 * hierarchy on reads.
365 * step down the hierarchy increments the level. This along with
367 * descendant of another without traversing the hierarchy.
434 * On the default hierarchy, a css_set for a cgroup with some
491 * A cgroup_root represents the root of a cgroup hierarchy, and may be
492 * associated with a kernfs_root to form an active hierarchy. This is
498 /* The bitmask of subsystems attached to this hierarchy */
501 /* Unique id for this hierarchy. */
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | cgroup-defs.h | 128 __CFTYPE_ONLY_ON_DFL = (1 << 16), /* only on default hierarchy */
129 __CFTYPE_NOT_ON_DFL = (1 << 17), /* not on default hierarchy */
249 * On the default hierarchy, ->subsys[ssid] may point to a css
310 * hierarchy on reads.
397 * step down the hierarchy increments the level. This along with
399 * descendant of another without traversing the hierarchy.
472 * On the default hierarchy, a css_set for a cgroup with some
533 * A cgroup_root represents the root of a cgroup hierarchy, and may be
534 * associated with a kernfs_root to form an active hierarchy. This is
540 /* The bitmask of subsystems attached to this hierarchy */
[all …]
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/ |
| D | landlock.rst | 32 file hierarchy, and the related filesystem actions are defined with `access
111 file hierarchy ``/usr``. Without another rule, write actions would then be
182 It is recommended setting access rights to file hierarchy leaves as much as
184 read-only hierarchy and ``~/tmp/`` as a read-write hierarchy, compared to
185 ``~/`` as a read-only hierarchy and ``~/tmp/`` as a read-write hierarchy.
224 A bind mount mirrors a source file hierarchy to a destination. The destination
225 hierarchy is then composed of the exact same files, on which Landlock rules can
232 combined in a merge directory, result of the mount point. This merge hierarchy
234 on the merge hierarchy only reflects on the upper layer. From a Landlock
238 restrict the resulted merged hierarchy, and vice versa. Landlock users should
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 104 distribute system resources along the hierarchy in a controlled and
110 distributing a specific type of system resource along the hierarchy
125 sub-hierarchy of the cgroup. When a controller is enabled on a nested
127 restrictions set closer to the root in the hierarchy can not be
137 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
138 hierarchy can be mounted with the following mount command::
143 controllers which support v2 and are not bound to a v1 hierarchy are
144 automatically bound to the v2 hierarchy and show up at the root.
145 Controllers which are not in active use in the v2 hierarchy can be
146 bound to other hierarchies. This allows mixing v2 hierarchy with the
[all …]
|
| /kernel/linux/linux-6.6/fs/9p/ |
| D | v9fs.h | 18 * @V9FS_ACCESS_SINGLE: only the mounting user can access the hierarchy
93 * @uname: string user name to mount hierarchy as
94 * @aname: mount specifier for remote hierarchy
96 * @dfltuid: default numeric userid to mount hierarchy as
97 * @dfltgid: default numeric groupid to mount hierarchy as
98 * @uid: if %V9FS_ACCESS_SINGLE, the numeric uid which mounted the hierarchy
122 char *aname; /* name of remote hierarchy being mounted */
|
| /kernel/linux/linux-6.6/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 …]
|