From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Richard Henderson <richard.henderson@linaro.org>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
Russell King <linux@armlinux.org.uk>, Guo Ren <guoren@kernel.org>,
Michal Simek <monstr@monstr.eu>,
Dinh Nguyen <dinguyen@kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
Stafford Horne <shorne@gmail.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Helge Deller <deller@gmx.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Andrew Donnellan <ajd@linux.ibm.com>,
Benjamin Gray <bgray@linux.ibm.com>,
Frederic Weisbecker <frederic@kernel.org>,
Xin Li <xin3.li@intel.com>, Kees Cook <keescook@chromium.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Tony Battersby <tonyb@cybernetics.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Brian Gerst <brgerst@gmail.com>,
Leonardo Bras <leobras@redhat.com>,
Imran Khan <imran.f.khan@oracle.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Rik van Riel <riel@surriel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
David Vernet <void@manifault.com>,
Julia Lawall <julia.lawall@inria.fr>,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-openrisc@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, linux-pm@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH v2 00/14] Introducing TIF_NOTIFY_IPI flag
Date: Sat, 15 Jun 2024 03:45:21 +0200 [thread overview]
Message-ID: <20240615014521.GR8774@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240615012814.GP8774@noisy.programming.kicks-ass.net>
On Sat, Jun 15, 2024 at 03:28:14AM +0200, Peter Zijlstra wrote:
> On Fri, Jun 14, 2024 at 12:48:37PM +0200, Vincent Guittot wrote:
> > The main problem is that need_resched becomes somewhat meaningless
> > because it doesn't only mean "I need to resched a task" and we have
> > to add more tests around even for those not using polling
>
> True, however we already had some of that by having the wakeup list,
> that made nr_running less 'reliable'.
Doesn't using !idle_cpu() instead of need_resched() in those balance
paths already do the right thing?
Checking need_resched() as an indicator of it getting work is already a
bit an assumption.
Also, Ingo, idle_cpu() and friends don't really belong in syscalls.c...
next prev parent reply other threads:[~2024-06-15 1:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 18:15 [PATCH v2 00/14] Introducing TIF_NOTIFY_IPI flag K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 01/14] thread_info: Add helpers to test and clear TIF_NOTIFY_IPI K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 02/14] sched: Define a need_resched_or_ipi() helper and use it treewide K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 03/14] sched/core: Use TIF_NOTIFY_IPI to notify an idle CPU in TIF_POLLING mode of pending IPI K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 04/14] x86/thread_info: Introduce TIF_NOTIFY_IPI flag K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 05/14] arm/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 06/14] alpha/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 07/14] openrisc/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 08/14] powerpc/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 09/14] sh/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 10/14] sparc/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 11/14] csky/thread_info: " K Prateek Nayak
2024-06-15 17:13 ` Guo Ren
2024-06-13 18:16 ` [PATCH v2 12/14] parisc/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 13/14] nios2/thread_info: " K Prateek Nayak
2024-06-13 18:16 ` [PATCH v2 14/14] microblaze/thread_info: " K Prateek Nayak
2024-06-14 9:28 ` [PATCH v2 00/14] Introducing " Peter Zijlstra
2024-06-14 10:48 ` Vincent Guittot
2024-06-14 16:31 ` Chen Yu
2024-06-17 8:33 ` K Prateek Nayak
2024-06-18 7:49 ` Chen Yu
2024-06-18 18:33 ` K Prateek Nayak
2024-06-20 7:30 ` Chen Yu
2024-06-15 1:28 ` Peter Zijlstra
2024-06-15 1:45 ` Peter Zijlstra [this message]
2024-06-16 14:57 ` Vincent Guittot
2024-06-17 5:52 ` K Prateek Nayak
2024-06-15 1:42 ` Peter Zijlstra
2024-06-15 14:26 ` Russell King (Oracle)
2024-06-17 4:35 ` K Prateek Nayak
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=20240615014521.GR8774@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ajd@linux.ibm.com \
--cc=andreas@gaisler.com \
--cc=bgray@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dalias@libc.org \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=dietmar.eggemann@arm.com \
--cc=dinguyen@kernel.org \
--cc=frederic@kernel.org \
--cc=gautham.shenoy@amd.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guoren@kernel.org \
--cc=hpa@zytor.com \
--cc=imran.f.khan@oracle.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jonas@southpole.se \
--cc=julia.lawall@inria.fr \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=kprateek.nayak@amd.com \
--cc=leobras@redhat.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mattst88@gmail.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=rafael@kernel.org \
--cc=richard.henderson@linaro.org \
--cc=rick.p.edgecombe@intel.com \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--cc=shorne@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=tonyb@cybernetics.com \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
--cc=xin3.li@intel.com \
--cc=ysato@users.sourceforge.jp \
/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