From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: <elver@google.com>, <catalin.marinas@arm.com>, <will@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: <linux-doc@vger.kernel.org>, <arnd@arndb.de>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v4 0/2] arm64: Fix kcsan test_barrier fail and panic
Date: Mon, 23 May 2022 19:31:24 +0800 [thread overview]
Message-ID: <20220523113126.171714-1-wangkefeng.wang@huawei.com> (raw)
Fix selftest and kcsan_test() module fail when KCSAN_STRICT
and KCSAN_WEAK_MEMORY enabled on ARM64.
v4:
- Use 2 spaces after a sentence-ending '.', suggested by Marco
- Collect Ack/Review
v3:
- update dma_mb()'s description and add the generic definition,
also asm-generic change is moved into patch1, suggested by Marco.
v2:
- Add documents about dma_mb(), suggested by Mike and Will.
- drop Fixes tag and update changlog, suggested by Mike.
Kefeng Wang (2):
asm-generic: Add memory barrier dma_mb()
arm64: kcsan: Support detecting more missing memory barriers
Documentation/memory-barriers.txt | 11 ++++++-----
arch/arm64/include/asm/barrier.h | 12 ++++++------
include/asm-generic/barrier.h | 8 ++++++++
3 files changed, 20 insertions(+), 11 deletions(-)
--
2.35.3
next reply other threads:[~2022-05-23 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 11:31 Kefeng Wang [this message]
2022-05-23 11:31 ` [PATCH v4 1/2] asm-generic: Add memory barrier dma_mb() Kefeng Wang
2022-05-23 11:35 ` Marco Elver
2022-06-16 23:13 ` Paul E. McKenney
2022-06-17 10:18 ` Marco Elver
2022-06-19 9:45 ` Catalin Marinas
2022-06-20 21:02 ` Paul E. McKenney
2022-05-23 11:38 ` Mark Rutland
2022-05-23 11:31 ` [PATCH v4 2/2] arm64: kcsan: Support detecting more missing memory barriers Kefeng Wang
2022-05-23 14:16 ` Mark Rutland
2022-06-14 3:20 ` Kefeng Wang
2022-06-21 10:46 ` Catalin Marinas
2022-06-23 19:31 ` [PATCH v4 0/2] arm64: Fix kcsan test_barrier fail and panic Will Deacon
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=20220523113126.171714-1-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=elver@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).