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: Tue, 11 Jul 2017 06:55:28 -0700 From: Christoph Hellwig <hch@...radead.org> To: Will Deacon <will.deacon@....com> Cc: Palmer Dabbelt <palmer@...belt.com>, hch@...radead.org, peterz@...radead.org, mingo@...hat.com, sfr@...b.auug.org.au, nicolas.dichtel@...nd.com, tklauser@...tanz.ch, james.hogan@...tec.com, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, mathieu.desnoyers@...icios.com Subject: Re: [PATCH 8/9] RISC-V: User-facing API On Tue, Jul 11, 2017 at 02:22:15PM +0100, Will Deacon wrote: > The problem is that by supporting these hypothetical designs that can't do > atomics, you hurt sensible designs that *can* do the atomics because you > force them to take an additional indirection that could otherwise be > avoided. Agreed. But the new patchset seems to remove it already, so I guess we're fine on the kernel side. Now we just need to make sure the glibc API doesn't use any indirections. Note that it might make sense to emit these for very low end nommu designs. Maybe even running Linux, but in that case they'll just need a special non-standard ABI for very limited use cases.
Powered by blists - more mailing lists