From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: Re: [PATCH] sched: Prevent raising SCHED_SOFTIRQ when CPU is !active
Date: Wed, 16 Dec 2020 11:10:12 +0100 [thread overview]
Message-ID: <87zh2erri3.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20201216081904.GK3040@hirez.programming.kicks-ass.net>
On Wed, Dec 16 2020 at 09:19, Peter Zijlstra wrote:
> On Tue, Dec 15, 2020 at 06:52:49PM +0100, Thomas Gleixner wrote:
>> I might be missing something, but how is the CPU which runs the pinned
>> kernel thread, i.e. the hotplug thread, supposed to go idle between the
>> two calls?
>
> Take a mutex or something other daft. My disabling preemption around it
> we basically assert the two functions are non-blocking and none of that
> cruft matters.
That'd be really daft, but yes we can do that for paranoia sake.
Thanks,
tglx
next prev parent reply other threads:[~2020-12-16 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 10:44 [PATCH] sched: Prevent raising SCHED_SOFTIRQ when CPU is !active Anna-Maria Behnsen
2020-12-15 11:18 ` Peter Zijlstra
2020-12-15 14:23 ` Anna-Maria Behnsen
2020-12-15 14:34 ` Steven Rostedt
2020-12-15 15:05 ` Peter Zijlstra
2020-12-15 17:52 ` Thomas Gleixner
2020-12-16 8:19 ` Peter Zijlstra
2020-12-16 10:10 ` Thomas Gleixner [this message]
2020-12-15 14:24 ` Steven Rostedt
2021-01-14 11:29 ` [tip: sched/core] " tip-bot2 for Anna-Maria Behnsen
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=87zh2erri3.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=bristot@redhat.com \
--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@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/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