Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753539AbdFVUiq (ORCPT ); Thu, 22 Jun 2017 16:38:46 -0400 Received: from ale.deltatee.com ([207.54.116.67]:54794 "EHLO ale.deltatee.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751149AbdFVUio (ORCPT ); Thu, 22 Jun 2017 16:38:44 -0400 To: Alan Cox References: <20170622164817.25515-1-logang@deltatee.com> <20170622164817.25515-4-logang@deltatee.com> <20170622211431.14270378@alans-desktop> <20170622213655.07dffac2@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 From: Logan Gunthorpe Message-ID: <131f6a1c-ee4d-20eb-d1d3-200c70bbae0c@deltatee.com> Date: Thu, 22 Jun 2017 14:38:28 -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: <20170622213655.07dffac2@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: 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 3/7] asm-generic/io.h: make ioread64 and iowrite64 universally available 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: 577 Lines: 14 On 6/22/2017 2:36 PM, Alan Cox wrote: > I think that makes sense for the platforms with that problem. I'm not > sure there are many that can't do it for mmio at least. 486SX can't do it > and I guess some ARM32 but I think almost everyone else can including > most 32bit x86. > > What's more of a problem is a lot of platforms can do 64bit MMIO via > ioread/write64 but not 64bit port I/O, and it's not clear how you > represent that via an ioread/write API that abstracts it away. In Patch 2, we call bad_io_access for anyone trying to do 64bit accesses on port I/O. Logan