From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>
Cc: sched-ext@meta.com, kernel-team@meta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] scx: Fix exit selftest to use custom DSQ
Date: Fri, 25 Oct 2024 07:04:05 -1000 [thread overview]
Message-ID: <ZxvPhYfWbz8WcBpg@slm.duckdns.org> (raw)
In-Reply-To: <20241025054014.66631-1-void@manifault.com>
On Fri, Oct 25, 2024 at 12:40:13AM -0500, David Vernet wrote:
> In commit 63fb3ec80516 ("sched_ext: Allow only user DSQs for
> scx_bpf_consume(), scx_bpf_dsq_nr_queued() and bpf_iter_scx_dsq_new()"), we
> updated the consume path to only accept user DSQs, thus making it invalid
> to consume SCX_DSQ_GLOBAL. This selftest was doing that, so let's create a
> custom DSQ and use that instead. The test now passes:
>
> [root@virtme-ng sched_ext]# ./runner -t exit
> ===== START =====
> TEST: exit
> DESCRIPTION: Verify we can cleanly exit a scheduler in multiple places
> OUTPUT:
> [ 12.387229] sched_ext: BPF scheduler "exit" enabled
> [ 12.406064] sched_ext: BPF scheduler "exit" disabled (unregistered from BPF)
> [ 12.453325] sched_ext: BPF scheduler "exit" enabled
> [ 12.474064] sched_ext: BPF scheduler "exit" disabled (unregistered from BPF)
> [ 12.515241] sched_ext: BPF scheduler "exit" enabled
> [ 12.532064] sched_ext: BPF scheduler "exit" disabled (unregistered from BPF)
> [ 12.592063] sched_ext: BPF scheduler "exit" disabled (unregistered from BPF)
> [ 12.654063] sched_ext: BPF scheduler "exit" disabled (unregistered from BPF)
> [ 12.715062] sched_ext: BPF scheduler "exit" disabled (unregistered from BPF)
> ok 1 exit #
> ===== END =====
>
> Signed-off-by: David Vernet <void@manifault.com>
Applied to sched_ext/for-6.12-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2024-10-25 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 5:40 David Vernet
2024-10-25 5:40 ` [PATCH 2/2] scx: Fix raciness in scx_ops_bypass() David Vernet
2024-10-25 19:39 ` Tejun Heo
2024-10-25 19:47 ` David Vernet
2024-10-25 17:04 ` 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=ZxvPhYfWbz8WcBpg@slm.duckdns.org \
--to=tj@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@meta.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
all inboxes | Powered by JetHome®