From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
fweisbec@gmail.com, oleg@redhat.com
Subject: [PATCH tip/core/rcu 0/3] Updates to sys_membarrier for v4.14 to add registration
Date: Wed, 4 Oct 2017 14:37:34 -0700 [thread overview]
Message-ID: <20171004213734.GA11463@linux.vnet.ibm.com> (raw)
Hello!
This post-merge-window series fixes a problem that arose when designing
requested extensions to sys_membarrier() to allow JITs to efficiently
flush old code from instruction caches. Several potential algorithms are
much less painful if the user register intent to use this functionality
early on, for example, before the process spawns the second thread.
Registering at this time removes the need to interrupt each and every
thread in that process at the first expedited sys_membarrier() system
call.
However, if we let the current function out, then user programs might
be written without registration, which would make it more difficult to
add required registration after the fact. Hence the late-in-merge-window
request. (Ingo, pull request on its way as well.)
1. Provide register expedited private command.
2. Test private expedited cmd.
3. Document scheduler barrier requirements.
All courtesy of Mathieu Desnoyers.
Thanx, Paul
------------------------------------------------------------------------
MAINTAINERS | 2
arch/powerpc/Kconfig | 1
arch/powerpc/include/asm/membarrier.h | 43 +++++++
arch/powerpc/include/asm/thread_info.h | 3
arch/powerpc/kernel/Makefile | 2
arch/powerpc/kernel/membarrier.c | 45 +++++++
arch/powerpc/mm/mmu_context.c | 7 +
arch/x86/mm/tlb.c | 5
fs/exec.c | 1
include/linux/mm_types.h | 3
include/linux/sched/mm.h | 55 +++++++++
include/uapi/linux/membarrier.h | 23 ++--
init/Kconfig | 3
kernel/fork.c | 2
kernel/sched/core.c | 47 ++++----
kernel/sched/membarrier.c | 25 +++-
tools/testing/selftests/membarrier/membarrier_test.c | 109 ++++++++++++++++---
17 files changed, 329 insertions(+), 47 deletions(-)
next reply other threads:[~2017-10-04 21:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 21:37 Paul E. McKenney [this message]
2017-10-04 21:37 ` [PATCH tip/core/rcu 1/3] membarrier: Provide register expedited private command Paul E. McKenney
2017-10-05 4:23 ` Nicholas Piggin
2017-10-05 12:22 ` Avi Kivity
2017-10-05 15:54 ` Mathieu Desnoyers
2017-10-05 15:53 ` Mathieu Desnoyers
2017-10-05 12:12 ` Peter Zijlstra
2017-10-05 12:24 ` Peter Zijlstra
2017-10-05 16:05 ` Mathieu Desnoyers
2017-10-05 16:02 ` Mathieu Desnoyers
2017-10-05 16:21 ` Peter Zijlstra
2017-10-05 21:44 ` Mathieu Desnoyers
2017-10-05 22:02 ` Andrea Parri
2017-10-05 22:19 ` Mathieu Desnoyers
2017-10-05 22:46 ` Steven Rostedt
2017-10-06 8:32 ` Peter Zijlstra
2017-10-07 15:10 ` Andrea Parri
2017-10-04 21:37 ` [PATCH tip/core/rcu 2/3] membarrier: selftest: Test private expedited cmd Paul E. McKenney
2017-10-04 21:37 ` [PATCH tip/core/rcu 3/3] membarrier: Document scheduler barrier requirements Paul E. McKenney
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=20171004213734.GA11463@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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