From: Thomas Gleixner <tglx@linutronix.de>
To: Rasmus Villemoes <ravi@prevas.dk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>,
Ingo Molnar <mingo@kernel.org.com>,
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>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [patch 2/2] sched/ext: Remove sched_fork() hack
Date: Mon, 28 Oct 2024 13:58:59 +0100 [thread overview]
Message-ID: <87o7342xkc.ffs@tglx> (raw)
In-Reply-To: <87zfmojtpk.fsf@prevas.dk>
On Mon, Oct 28 2024 at 13:30, Rasmus Villemoes wrote:
>> + memset(scx, 0, sizeof(*scx));
>> INIT_LIST_HEAD(&scx->dsq_list.node);
>> RB_CLEAR_NODE(&scx->dsq_priq);
>> scx->sticky_cpu = -1;
>
> Should the "must be the last" comment in include/linux/sched/ext.h also
> be removed?
Oh. Indeed. I missed that one.
Thanks for pointing it out.
tglx
next prev parent reply other threads:[~2024-10-28 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 10:43 [patch 0/2] sched: Cleanup idle task double initialization Thomas Gleixner
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 [this message]
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=87o7342xkc.ffs@tglx \
--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=ravi@prevas.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.