[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxvPhYfWbz8WcBpg@slm.duckdns.org>
Date: Fri, 25 Oct 2024 07:04:05 -1000
From: Tejun Heo <tj@...nel.org>
To: David Vernet <void@...ifault.com>
Cc: sched-ext@...a.com, kernel-team@...a.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] scx: Fix exit selftest to use custom DSQ
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@...tme-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@...ifault.com>
Applied to sched_ext/for-6.12-fixes.
Thanks.
--
tejun
Powered by blists - more mailing lists