From: Tejun Heo <tj@kernel.org>
To: "Zhangqiao (2012 lab)" <zhangqiao22@huawei.com>
Cc: void@manifault.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-6.11] sched_ext: Reverting @p->sched_class if @p->disallow is set
Date: Wed, 17 Jul 2024 07:49:58 -1000 [thread overview]
Message-ID: <ZpgERphu--gPn235@slm.duckdns.org> (raw)
In-Reply-To: <cd3fa16d-5a70-4c85-a591-fa4fa481f50b@huawei.com>
On Wed, Jul 17, 2024 at 10:01:13AM +0800, Zhangqiao (2012 lab) wrote:
> > Ah, I see what you mean. I was referring to the classs switching operations
> > in scx_ops_enable(). You're looking at the fork path. I don't think we can
>
> Yes, i was referring to the fork path.
>
> > switch sched_class at that point and the .disallow mechanism is there to
> > allow the scheduler to filter out tasks on scheduler start. I'll update the
> > code so that .disallow is only allowed during the initial attach.
So, something like this.
Thanks.
diff --git a/include/linux/sched/ext.h b/include/linux/sched/ext.h
index 593d2f4909dd..a4aa516cee7d 100644
--- a/include/linux/sched/ext.h
+++ b/include/linux/sched/ext.h
@@ -181,11 +181,12 @@ struct sched_ext_entity {
* If set, reject future sched_setscheduler(2) calls updating the policy
* to %SCHED_EXT with -%EACCES.
*
- * If set from ops.init_task() and the task's policy is already
- * %SCHED_EXT, which can happen while the BPF scheduler is being loaded
- * or by inhering the parent's policy during fork, the task's policy is
- * rejected and forcefully reverted to %SCHED_NORMAL. The number of
- * such events are reported through /sys/kernel/debug/sched_ext::nr_rejected.
+ * Can be set from ops.init_task() while the BPF scheduler is being
+ * loaded (!scx_init_task_args->fork). If set and the task's policy is
+ * already %SCHED_EXT, the task's policy is rejected and forcefully
+ * reverted to %SCHED_NORMAL. The number of such events are reported
+ * through /sys/kernel/debug/sched_ext::nr_rejected. Setting this flag
+ * during fork is not allowed.
*/
bool disallow; /* reject switching into SCX */
diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
index da9cac6b6cc2..cf60474efa75 100644
--- a/kernel/sched/ext.c
+++ b/kernel/sched/ext.c
@@ -3399,18 +3399,17 @@ static int scx_ops_init_task(struct task_struct *p, struct task_group *tg, bool
scx_set_task_state(p, SCX_TASK_INIT);
- if (p->scx.disallow) {
+ if (!fork && p->scx.disallow) {
struct rq *rq;
struct rq_flags rf;
rq = task_rq_lock(p, &rf);
/*
- * We're either in fork or load path and @p->policy will be
- * applied right after. Reverting @p->policy here and rejecting
- * %SCHED_EXT transitions from scx_check_setscheduler()
- * guarantees that if ops.init_task() sets @p->disallow, @p can
- * never be in SCX.
+ * We're in the load path and @p->policy will be applied right
+ * after. Reverting @p->policy here and rejecting %SCHED_EXT
+ * transitions from scx_check_setscheduler() guarantees that if
+ * ops.init_task() sets @p->disallow, @p can never be in SCX.
*/
if (p->policy == SCHED_EXT) {
p->policy = SCHED_NORMAL;
@@ -3418,6 +3417,9 @@ static int scx_ops_init_task(struct task_struct *p, struct task_group *tg, bool
}
task_rq_unlock(rq, p, &rf);
+ } else if (p->scx.disallow) {
+ scx_ops_error("ops.init_task() set task->scx.disallow for %s[%d] during fork",
+ p->comm, p->pid);
}
p->scx.flags |= SCX_TASK_RESET_RUNNABLE_AT;
--
tejun
next prev parent reply other threads:[~2024-07-17 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 11:07 [PATCH sched_ext/for-6.11] sched_ext: Reverting @p->sched_class if @p->disallow is set Zhangqiao (2012 lab)
2024-07-11 18:57 ` Tejun Heo
2024-07-16 11:32 ` Zhangqiao (2012 lab)
2024-07-16 20:48 ` Tejun Heo
2024-07-17 2:01 ` Zhangqiao (2012 lab)
2024-07-17 17:49 ` Tejun Heo [this message]
2024-07-18 6:04 ` Zhangqiao (2012 lab)
2024-07-31 19:14 ` [PATCH sched_ext/for-6.12] sched_ext: Allow p->scx.disallow only while loading Tejun Heo
2024-07-31 20:33 ` David Vernet
2024-08-01 23:32 ` [PATCH v2 " Tejun Heo
2024-08-02 0:21 ` David Vernet
2024-08-02 18:59 ` 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=ZpgERphu--gPn235@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.com \
--cc=zhangqiao22@huawei.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