From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Ingo Molnar <mingo@kernel.org.com>
Subject: [patch 0/2] sched: Cleanup idle task double initialization
Date: Mon, 28 Oct 2024 11:43:40 +0100 (CET) [thread overview]
Message-ID: <20241028103006.008053168@linutronix.de> (raw)
Idle tasks are initialized via __sched_fork() twice, which can be trivially
avoided as pointed out here:
https://lore.kernel.org/all/8734p4ymqj.ffs@tglx
As this got ignored, the tasteless hack in init_scx_entity() to work around
it stayed and found it's way into mainline.
Mop it up after the fact to not further proliferate technical debt.
Thanks,
tglx
---
core.c | 13 ++++---------
ext.c | 7 +------
2 files changed, 5 insertions(+), 15 deletions(-)
next reply other threads:[~2024-10-28 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 10:43 Thomas Gleixner [this message]
2024-10-28 10:43 ` [patch 1/2] sched: Initialize idle tasks only once Thomas Gleixner
2024-11-06 10:48 ` [tip: sched/core] " tip-bot2 for Thomas Gleixner
2024-10-28 10:43 ` [patch 2/2] sched/ext: Remove sched_fork() hack Thomas Gleixner
2024-10-28 12:30 ` Rasmus Villemoes
2024-10-28 12:58 ` Thomas Gleixner
2024-10-28 13:20 ` [patch v1A " Thomas Gleixner
2024-10-28 17:37 ` Tejun Heo
2024-11-06 10:48 ` [tip: sched/core] " tip-bot2 for Thomas Gleixner
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=20241028103006.008053168@linutronix.de \
--to=tglx@linutronix.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@kernel.org.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.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®