Home
last modified time | relevance | path

Searched refs:unified (Results 1 – 14 of 14) sorted by relevance

/systemd-251/src/shared/
Dcgroup-setup.c427 int r, unified; in cg_set_access() local
434 unified = cg_unified_controller(controller); in cg_set_access()
435 if (unified < 0) in cg_set_access()
436 return unified; in cg_set_access()
448 for (i = attributes[unified]; i->name; i++) { in cg_set_access()
/systemd-251/docs/
DCGROUP_DELEGATION.md27 [unified cgroup hierarchy](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html).
99 3. **Hybrid** — this is a hybrid between the unified and legacy mode. It's set
101 `/sys/fs/cgroup/unified/` that contains the cgroup v2 hierarchy. (Note that in
102 this mode the unified hierarchy won't have controllers attached, the
104 i.e. `/sys/fs/cgroup/unified/` is purely and exclusively about core cgroup v2
111 software today and don't focus on the unified mode, then you are writing
121 conceptually very close to the unified hierarchy. In particular this allows us
131 `.f_type` field, then you are in unified mode. If it reports `TMPFS_MAGIC` then
133 `statfs()` again on `/sys/fs/cgroup/unified/`. If that succeeds and reports
136 `stat -f /sys/fs/cgroup/unified`.
[all …]
DBOOT_LOADER_SPECIFICATION.md326 A unified kernel image is a single EFI PE executable combining an EFI stub
329 [dracut(8)](http://man7.org/linux/man-pages/man8/dracut.8.html). Such unified
343 A valid unified kernel image must contain two PE sections:
381 menu with this. On EFI, it then extends this with any unified kernel images
DPORTABLE_SERVICES.md232 single, unified image that:
DENVIRONMENT.md125 unified cgroup hierarchy mode.
DCONTAINER_INTERFACE.md77 cgroup sub-tree of the container itself (on cgroupv2 in the unified
DUSER_RECORD.md41 user records. It also provides a unified [Varlink](https://varlink.org/) API
/systemd-251/test/TEST-56-EXIT-TYPE/
Dtest.sh9 if [[ "$(get_cgroup_hierarchy)" != unified ]]; then
/systemd-251/src/basic/
Dcgroup-util.c694 int unified, r; in cg_pid_get_path() local
705 unified = cg_unified_controller(controller); in cg_pid_get_path()
706 if (unified < 0) in cg_pid_get_path()
707 return unified; in cg_pid_get_path()
708 if (unified == 0) { in cg_pid_get_path()
732 if (unified) { in cg_pid_get_path()
/systemd-251/test/test-umount/
Drhbug-1554943.mountinfo9 26 25 0:23 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:5 - cgroup2 cgroup rw
/systemd-251/
Dmeson_options.txt210 choices : ['legacy', 'hybrid', 'unified'], value : 'unified',
DTODO100 unified kernel binaries. This section should be picked up by sd-stub, and
111 are stored in PE sections of their own too. Building a unified kernel would
114 sd-stub, raw kernel image, raw initrd, and PCR signature into a unified
211 - kernel-install should be able to install pre-built unified kernel images in
312 drop it into the unified kernel dir in the ESP. And bam you have something
313 that is tiny, feels a lot like a unified kernel, but all it does is chainload
318 sd-stub, so that machine ID is stable even on systems where unified kernels
1423 - teach it to copy in unified kernel images and maybe type #1 boot loader spec entries from host
DNEWS336 confidentiality). The credentials that can be passed to unified
1114 complete EFI unified kernel image, implementing Boot Loader
2146 unified v2 cgroup hierarchy is used, and "v1" means that legacy v1
3835 produced, extended and consumed in unified form. We hope that
3848 The complete user record data is unified with the home directory,
4405 * systemd now defaults to the "unified" cgroup hierarchy setup during
4406 build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
5342 kernel 4.15+ and the unified cgroup hierarchy, as required accounting
5349 using the unified cgroup hierarchy, unless one explicitly passes
7129 /sys/fs/cgroup/unified. This should provide a large degree of
[all …]
/systemd-251/test/
Dtest-functions2078 …if [[ -d /sys/fs/cgroup/unified && "$(stat -c '%T' -f /sys/fs/cgroup/unified)" == cgroup2fs ]]; th…