From: Peter Zijlstra <peterz@infradead.org>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
tglx@linutronix.de, bristot@redhat.com, yejune.deng@gmail.com
Subject: Re: [PATCH 0/2] sched: Address idle task vs pcpu kthread checks
Date: Wed, 12 May 2021 13:00:06 +0200 [thread overview]
Message-ID: <YJu1NpMt3BcLYGHh@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210510151024.2448573-1-valentin.schneider@arm.com>
On Mon, May 10, 2021 at 04:10:22PM +0100, Valentin Schneider wrote:
> Note: I remember seeing some patch(es) from Peter tackling this exact
> problem, but I couldn't find them again.
Found it (by accident), yours is nicer though :-)
> Valentin Schneider (1):
> sched: Make the idle task quack like a per-CPU kthread
>
> Yejune Deng (1):
> lib/smp_processor_id: Use is_percpu_thread() instead of
> nr_cpus_allowed
>
> include/linux/kthread.h | 2 ++
> kernel/kthread.c | 30 ++++++++++++++++++------------
> kernel/sched/core.c | 21 +++++++++++++++------
> lib/smp_processor_id.c | 6 +-----
> 4 files changed, 36 insertions(+), 23 deletions(-)
Thanks!
prev parent reply other threads:[~2021-05-12 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 15:10 Valentin Schneider
2021-05-10 15:10 ` [PATCH 1/2] sched: Make the idle task quack like a per-CPU kthread Valentin Schneider
2021-05-10 15:57 ` Valentin Schneider
2021-05-11 7:32 ` Ingo Molnar
2021-05-11 9:33 ` Valentin Schneider
2021-05-19 8:09 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2021-05-10 15:10 ` [PATCH 2/2] lib/smp_processor_id: Use is_percpu_thread() instead of nr_cpus_allowed Valentin Schneider
2021-05-19 8:09 ` [tip: sched/core] " tip-bot2 for Yejune Deng
2021-05-19 9:02 ` tip-bot2 for Yejune Deng
2021-05-31 10:21 ` [PATCH] sched,init: Fix DEBUG_PREEMPT vs early boot Peter Zijlstra
2021-06-01 11:54 ` Valentin Schneider
2021-06-01 14:04 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2021-05-12 11:00 ` Peter Zijlstra [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=YJu1NpMt3BcLYGHh@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
--cc=yejune.deng@gmail.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®