From: Richard Palethorpe <rpalethorpe@suse.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Question on .needs_cgroup_ctrls for cgroupv2
Date: Mon, 27 Feb 2023 15:52:59 +0000 [thread overview]
Message-ID: <87bklfay0l.fsf@suse.de> (raw)
In-Reply-To: <Y/zMBSx4p3gqRC3J@yuki>
Hello,
Cyril Hrubis <chrubis@suse.cz> writes:
> Hi!
>> So .needs_cgroup_ctrls can not used anymore for ONLY V2 case?
>> Since i encounter "tst_cgroup.c:848: TCONF: V2 'memory' controller
>> required, but it's mounted on V1" when i add ".needs_cgroup_ctrls =
>> (const char *const []){ "memory", NULL }".
You should see this works fine on Tumbleweed where pure V2 is the
default.
>
> Each controller can be mounted as V1 or as V2 but not both at the same
> time. It depends on how the system is booted, the default on most
> distributions is mixed V1 and V2 at the moment. If you want V2 system
> you have to reboot with systemd.unified_cgroup_hierarchy=1.
Yes that is the kernel command line option which you can add through
GRUB (unless I am mistaken).
Or it can be specified in the systemd configuration somewhere.
LTP does not try to remount CGroups if a controller is not on the
required version. If you need to test the unified hierarchy or a V2
controller then the simplest thing to do is configure systemd to only
use V2 (unified).
The exception is if the needed controller is not mounted already, then
LTP will mount it. This is the case if you, for e.g., use Rapido or some
buildroot config with CGroups in the kernel, but not userland.
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-02-27 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 14:44 [LTP] Question on .needs_cgroup_ctrls for cgroupv2 Wei Gao via ltp
2023-02-27 14:58 ` Cyril Hrubis
2023-02-27 15:17 ` Wei Gao via ltp
2023-02-27 15:28 ` Cyril Hrubis
2023-02-27 15:52 ` Richard Palethorpe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bklfay0l.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox