From: Will Deacon Subject: Re: [PATCH RFC 0/3] API for 128-bit IO access Date: Wed, 24 Jan 2018 10:22:13 +0000 Message-ID: <20180124102212.GC20586@arm.com> References: <20180124090519.6680-1-ynorov@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Al Viro , Andrew Morton , Andrew Pinski , Arnd Bergmann , Catalin Marinas , "David S . Miller" , Geethasowjanya Akula , Greg Kroah-Hartman , Ingo Molnar , Kees Cook , Laura Abbott , Nicholas Piggin , Sunil Goutham To: Yury Norov Return-path: Content-Disposition: inline In-Reply-To: <20180124090519.6680-1-ynorov@caviumnetworks.com> Sender: linux-arch-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote: > This series adds API for 128-bit memory IO access and enables it for ARM64. > The original motivation for 128-bit API came from new Cavium network device > driver. The hardware requires 128-bit access to make things work. See > description in patch 3 for details. > > Also, starting from ARMv8.4, stp and ldp instructions become atomic, and > API for 128-bit access would be helpful in core arm64 code. Only for normal, cacheable memory, so they're not suitable for IO accesses as you're proposing here. Will