From: Will Deacon <will.deacon@arm.com>
To: linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, andrew.murray@arm.com,
arnd@arndb.de, catalin.marinas@arm.com,
Will Deacon <will.deacon@arm.com>
Subject: [PATCH 2/2] arm64: io: Hook up __io_par() for inX() ordering
Date: Mon, 11 Feb 2019 17:45:44 +0000 [thread overview]
Message-ID: <20190211174544.4302-3-will.deacon@arm.com> (raw)
In-Reply-To: <20190211174544.4302-1-will.deacon@arm.com>
Ensure that inX() provides the same ordering guarantees as readX()
by hooking up __io_par() so that it maps directly to __iormb().
Reported-by: Andrew Murray <andrew.murray@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
arch/arm64/include/asm/io.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/include/asm/io.h b/arch/arm64/include/asm/io.h
index ee723835c1f4..2985febe63ec 100644
--- a/arch/arm64/include/asm/io.h
+++ b/arch/arm64/include/asm/io.h
@@ -121,6 +121,7 @@ static inline u64 __raw_readq(const volatile void __iomem *addr)
: "memory"); \
})
+#define __io_par __iormb
#define __iowmb() wmb()
#define mmiowb() do { } while (0)
--
2.11.0
next prev parent reply other threads:[~2019-02-11 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:45 [PATCH 0/2] Ensure inX() is ordered wrt delay() routines Will Deacon
2019-02-11 17:45 ` [PATCH 1/2] asm-generic/io: Pass result on inX() accessor to __io_par() Will Deacon
2019-02-12 11:55 ` Arnd Bergmann
2019-02-13 17:46 ` Will Deacon
2019-02-13 20:59 ` Arnd Bergmann
2019-02-13 21:57 ` Palmer Dabbelt
2019-02-18 15:56 ` Will Deacon
2019-02-11 17:45 ` Will Deacon [this message]
2019-02-12 10:42 ` [PATCH 2/2] arm64: io: Hook up __io_par() for inX() ordering Geert Uytterhoeven
2019-02-13 17:25 ` 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=20190211174544.4302-3-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=andrew.murray@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.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).