Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753460AbdFVUKP (ORCPT ); Thu, 22 Jun 2017 16:10:15 -0400 Received: from ale.deltatee.com ([207.54.116.67]:54710 "EHLO ale.deltatee.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753362AbdFVUKN (ORCPT ); Thu, 22 Jun 2017 16:10:13 -0400 To: Alan Cox References: <20170622164817.25515-1-logang@deltatee.com> <20170622164817.25515-5-logang@deltatee.com> <20170622210828.27304f6a@alans-desktop> Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-ntb@googlegroups.com, linux-alpha@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org, dri-devel@lists.freedesktop.org, Arnd Bergmann , Greg Kroah-Hartman , Stephen Bates , Richard Henderson , Ivan Kokshaysky , Matt Turner From: Logan Gunthorpe Message-ID: <401cdb64-6fdb-be30-b8bc-bf51c1a35074@deltatee.com> Date: Thu, 22 Jun 2017 14:09:55 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20170622210828.27304f6a@alans-desktop> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 172.16.1.111 X-SA-Exim-Rcpt-To: mattst88@gmail.com, ink@jurassic.park.msu.ru, rth@twiddle.net, sbates@raithlin.com, gregkh@linuxfoundation.org, arnd@arndb.de, dri-devel@lists.freedesktop.org, linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-alpha@vger.kernel.org, linux-ntb@googlegroups.com, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, gnomes@lxorguk.ukuu.org.uk X-SA-Exim-Mail-From: logang@deltatee.com Subject: Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on ale.deltatee.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 409 Lines: 10 On 6/22/2017 2:08 PM, Alan Cox wrote: > But this does not do the same thing as an ioread64 with regards to > atomicity or side effects on the device. The same is true of the other > hacks. You either have a real 64bit single read/write from MMIO space or > you don't. You can't fake it. Yes, I know. But is it not better than having every driver that wants to use these functions fake it themselves? Logan