From: zhidao su <soolaugust@gmail.com>
To: Andrea Righi <arighi@nvidia.com>
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH 1/2] sched_ext: Documentation: Document events sysfs file and module parameters
Date: Thu, 19 Mar 2026 00:04:54 -0700 (PDT) [thread overview]
Message-ID: <69bba016.170a0220.92228.ab0c@mx.google.com> (raw)
In-Reply-To: <abubiaubvpc2GqNH@gpd4>
On Thu, Mar 19, 2026 at 07:45:29AM +0100, Andrea Righi wrote:
> The right path is /sys/kernel/sched_ext/root/events. And now that we have
> sub-schedulers it's probably worth mentioning that sub-scheduler events
> file is located at /sys/kernel/sched_ext/root/sub/sub-<cgroup_id>/events.
Fixed in v2: the path is now /sys/kernel/sched_ext/root/events, and the
sub-scheduler path /sys/kernel/sched_ext/root/sub/sub-<cgroup_id>/events
is mentioned as well.
> Maybe ``sched_ext.`` namespace?
Fixed in v2.
Thanks for the review,
zhidao
next prev parent reply other threads:[~2026-03-19 7:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 5:30 [PATCH 1/2] sched_ext: Documentation: Document events sysfs file and module parameters zhidao su
2026-03-19 5:30 ` [PATCH 2/2] selftests/sched_ext: Return non-zero exit code on test failure zhidao su
2026-03-19 6:49 ` Andrea Righi
2026-03-19 6:45 ` [PATCH 1/2] sched_ext: Documentation: Document events sysfs file and module parameters Andrea Righi
2026-03-19 7:04 ` zhidao su [this message]
2026-03-19 7:01 ` [PATCH v2 0/2] sched_ext: documentation and selftest fixes zhidao su
2026-03-19 7:01 ` [PATCH v2 1/2] sched_ext: Documentation: Document events sysfs file and module parameters zhidao su
2026-03-19 7:01 ` [PATCH v2 2/2] selftests/sched_ext: Return non-zero exit code on test failure zhidao su
2026-03-21 18:42 ` [PATCH 1/2] sched_ext: Documentation: Document events sysfs file and module parameters Tejun Heo
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=69bba016.170a0220.92228.ab0c@mx.google.com \
--to=soolaugust@gmail.com \
--cc=arighi@nvidia.com \
--cc=sched-ext@lists.linux.dev \
/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