From: Tejun Heo <tj@kernel.org>
To: andrea.righi@linux.dev
Cc: David Vernet <void@manifault.com>,
Giovanni Gherdovich <giovanni.gherdovich@suse.com>,
Kleber Sacilotto de Souza <kleber.souza@canonical.com>,
Marcelo Henrique Cerri <marcelo.cerri@canonical.com>,
Phil Auld <pauld@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Provide a sysfs enable_seq counter
Date: Mon, 23 Sep 2024 06:53:29 -1000 [thread overview]
Message-ID: <ZvGdCQ1G5eoxEUX3@slm.duckdns.org> (raw)
In-Reply-To: <20240921193921.75594-1-andrea.righi@linux.dev>
On Sat, Sep 21, 2024 at 09:39:21PM +0200, andrea.righi@linux.dev wrote:
> From: Andrea Righi <andrea.righi@linux.dev>
>
> As discussed during the distro-centric session within the sched_ext
> Microconference at LPC 2024, introduce a sequence counter that is
> incremented every time a BPF scheduler is loaded.
>
> This feature can help distributions in diagnosing potential performance
> regressions by identifying systems where users are running (or have ran)
> custom BPF schedulers.
>
> Example:
>
> arighi@virtme-ng~> cat /sys/kernel/sched_ext/enable_seq
> 0
> arighi@virtme-ng~> sudo scx_simple
> local=1 global=0
> ^CEXIT: unregistered from user space
> arighi@virtme-ng~> cat /sys/kernel/sched_ext/enable_seq
> 1
>
> In this way user-space tools (such as Ubuntu's apport and similar) are
> able to gather and include this information in bug reports.
>
> Cc: Giovanni Gherdovich <giovanni.gherdovich@suse.com>
> Cc: Kleber Sacilotto de Souza <kleber.souza@canonical.com>
> Cc: Marcelo Henrique Cerri <marcelo.cerri@canonical.com>
> Cc: Phil Auld <pauld@redhat.com>
> Signed-off-by: Andrea Righi <andrea.righi@linux.dev>
Applied to sched_ext/for-6.12-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2024-09-23 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 19:39 [PATCH] sched_ext: Provide a sysfs enable_seq counter andrea.righi
2024-09-22 21:21 ` Tejun Heo
2024-09-23 10:45 ` Phil Auld
2024-09-23 15:14 ` Andrea Righi
2024-09-23 15:32 ` Tejun Heo
2024-09-23 16:00 ` Phil Auld
2024-09-23 16:34 ` Andrea Righi
2024-09-23 16:47 ` Tejun Heo
2024-09-23 16:57 ` Phil Auld
2024-09-23 17:01 ` Tejun Heo
2024-09-23 17:16 ` andrea.righi
2024-09-23 10:48 ` Phil Auld
2024-09-23 16:53 ` Tejun Heo [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=ZvGdCQ1G5eoxEUX3@slm.duckdns.org \
--to=tj@kernel.org \
--cc=andrea.righi@linux.dev \
--cc=giovanni.gherdovich@suse.com \
--cc=kleber.souza@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=pauld@redhat.com \
--cc=void@manifault.com \
/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