[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <131f6a1c-ee4d-20eb-d1d3-200c70bbae0c@deltatee.com>
Date: Thu, 22 Jun 2017 14:38:28 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Alan Cox <gnomes@...rguk.ukuu.org.uk>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
linux-ntb@...glegroups.com, linux-alpha@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-crypto@...r.kernel.org,
dri-devel@...ts.freedesktop.org, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stephen Bates <sbates@...thlin.com>
Subject: Re: [PATCH 3/7] asm-generic/io.h: make ioread64 and iowrite64
universally available
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
Powered by blists - more mailing lists