lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 22 Jun 2017 14:20:43 -0700 From: Richard Henderson <rth@...ddle.net> To: Logan Gunthorpe <logang@...tatee.com>, 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 Cc: Arnd Bergmann <arnd@...db.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Stephen Bates <sbates@...thlin.com>, Ivan Kokshaysky <ink@...assic.park.msu.ru>, Matt Turner <mattst88@...il.com> Subject: Re: [PATCH 4/7] alpha: provide ioread64 and iowrite64 implementations On 06/22/2017 09:48 AM, Logan Gunthorpe wrote: > Alpha implements its own io operation and doesn't use the > common library. Thus to make ioread64 and iowrite64 globally > available we need to add implementations for alpha. > > For this, we simply use calls that chain two 32-bit operations. > (mostly because I don't really understand the alpha architecture.) It's not difficult to provide this interface[*]. I believe the only reason I didn't do so from the beginning is that it wasn't used. r~ * At least for systems other than Jensen, which cannot generate 64-bit I/O. On the other hand, Jensen doesn't have PCI (EISA only), and so won't have any devices that care.
Powered by blists - more mailing lists