From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Anton Blanchard <anton@ozlabs.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH v2 0/4] membarrier fixes
Date: Wed, 2 Dec 2020 07:35:08 -0800 [thread overview]
Message-ID: <cover.1606923183.git.luto@kernel.org> (raw)
Hi all-
This is v2, and this time around everything is tagged for -stable.
Changes from v1:
- patch 1: comment fixes from Mathier
- patch 2: improved comments
- patch 3: split out as a separate patch
- patch 4: now has a proper explanation
Mathieu, I think we have to make sync_core sync the caller. See patch 4.
Andy Lutomirski (4):
x86/membarrier: Get rid of a dubious optimization
membarrier: Add an actual barrier before rseq_preempt()
membarrier: Explicitly sync remote cores when SYNC_CORE is requested
membarrier: Execute SYNC_CORE on the calling thread
arch/x86/include/asm/sync_core.h | 9 ++--
arch/x86/mm/tlb.c | 10 ++++-
kernel/sched/membarrier.c | 75 ++++++++++++++++++++++++--------
3 files changed, 71 insertions(+), 23 deletions(-)
--
2.28.0
next reply other threads:[~2020-12-02 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:35 Andy Lutomirski [this message]
2020-12-02 15:35 ` [PATCH v2 1/4] x86/membarrier: Get rid of a dubious optimization Andy Lutomirski
2020-12-02 15:35 ` [PATCH v2 2/4] membarrier: Add an actual barrier before rseq_preempt() Andy Lutomirski
2020-12-02 19:40 ` Mathieu Desnoyers
2020-12-02 15:35 ` [PATCH v2 3/4] membarrier: Explicitly sync remote cores when SYNC_CORE is requested Andy Lutomirski
2020-12-02 19:43 ` Mathieu Desnoyers
2020-12-02 15:35 ` [PATCH v2 4/4] membarrier: Execute SYNC_CORE on the calling thread Andy Lutomirski
2020-12-02 19:39 ` Mathieu Desnoyers
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=cover.1606923183.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=anton@ozlabs.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=npiggin@gmail.com \
--cc=x86@kernel.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