From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: torvalds@linux-foundation.org
Cc: mingo@kernel.org, mathieu.desnoyers@efficios.com,
peterz@infradead.org, boqun.feng@gmail.com, ahh@google.com,
maged.michael@gmail.com, gromer@google.com, avi@scylladb.com,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
davejwatson@fb.com, stern@rowland.harvard.edu,
will.deacon@arm.com, luto@kernel.org, viro@zeniv.linux.org.uk,
npiggin@gmail.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL urgent-membarrier] membarrier commits for 4.14
Date: Wed, 18 Oct 2017 12:59:44 -0700 [thread overview]
Message-ID: <20171018195944.GA15331@linux.vnet.ibm.com> (raw)
Hello, Linus,
This urgent pull request contains five commits that fix 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
pull request.
The last two commits remove unused code from architectures not supporting
sys_membarrier() and fix a problem that arises when tasks are created
with CLONE_VM but !CLONE_THREAD on powerpc.
These have been subject to 0day test robot and -next testing and
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git membarrier.2017.10.09a
for you to fetch changes up to f7399e01ccd0850786bdedbee2fd351651ce99f8:
Fix: membarrier: Handle CLONE_VM + !CLONE_THREAD correctly on powerpc (2017-10-09 14:24:49 -0700)
----------------------------------------------------------------
Mathieu Desnoyers (5):
membarrier: Provide register expedited private command
membarrier: selftest: Test private expedited cmd
membarrier: Document scheduler barrier requirements
membarrier: Remove unused code for architectures without membarrier hooks
Fix: membarrier: Handle CLONE_VM + !CLONE_THREAD correctly on powerpc
MAINTAINERS | 2 +
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/membarrier.h | 26 +++++
arch/powerpc/kernel/Makefile | 2 +
arch/powerpc/kernel/membarrier.c | 36 +++++++
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 | 37 +++++++
include/uapi/linux/membarrier.h | 23 +++--
init/Kconfig | 3 +
kernel/sched/core.c | 47 +++++----
kernel/sched/membarrier.c | 35 ++++++-
.../testing/selftests/membarrier/membarrier_test.c | 109 ++++++++++++++++++---
15 files changed, 290 insertions(+), 47 deletions(-)
create mode 100644 arch/powerpc/include/asm/membarrier.h
create mode 100644 arch/powerpc/kernel/membarrier.c
next reply other threads:[~2017-10-18 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 19:59 Paul E. McKenney [this message]
2017-10-19 17:30 ` [GIT PULL urgent-membarrier] membarrier commits for 4.14 Mathieu Desnoyers
2017-10-19 17:30 ` Mathieu Desnoyers
2017-10-19 20:24 ` Linus Torvalds
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=20171018195944.GA15331@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ahh@google.com \
--cc=avi@scylladb.com \
--cc=benh@kernel.crashing.org \
--cc=boqun.feng@gmail.com \
--cc=davejwatson@fb.com \
--cc=gromer@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maged.michael@gmail.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).