From: Logan Gunthorpe Subject: Re: [PATCH 2/7] iomap: implement ioread64 and iowrite64 Date: Mon, 26 Jun 2017 15:25:41 -0600 Message-ID: <0746dbb0-9fc1-d24c-89c0-b079a3cd0c7b@deltatee.com> References: <20170622164817.25515-1-logang@deltatee.com> <20170622164817.25515-3-logang@deltatee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux Kernel Mailing List , linux-arch , linux-ntb@googlegroups.com, linux-alpha@vger.kernel.org, linuxppc-dev , linux-crypto@vger.kernel.org, dri-devel , Greg Kroah-Hartman , Stephen Bates , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Suresh Warrier , Nicholas Piggin To: Arnd Bergmann Return-path: In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On 6/26/2017 2:43 PM, Arnd Bergmann wrote: > This hardcodes the behavior of include/linux/io-64-nonatomic-hi-lo.h, which > I find rather confusing, as only about one in five drivers wants this > behavior. > > I'd suggest you don't add it in lib/iomap.c at all for 32-bit architectures, > but rather use the same logic that we have for readq/writeq in > io-64-nonatomic-hi-lo.h and io-64-nonatomic-lo-hi.h, adding > {lo_hi,hi_lo}_{ioread,iowrite}{,be} to the same files, and provide > the {ioread,iowrite}{,be} macros only if they have not been defined > at that point. Thanks Arnd. Yes, I'm already reworking this patchset to do exactly that. Logan