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, 7 Oct 2014 16:59:03 -0700 From: David Daney <ddaney@...iumnetworks.com> To: Ralf Baechle <ralf@...ux-mips.org> CC: Rich Felker <dalias@...c.org>, David Daney <ddaney.cavm@...il.com>, <libc-alpha@...rceware.org>, <linux-kernel@...r.kernel.org>, <linux-mips@...ux-mips.org>, David Daney <david.daney@...ium.com> Subject: Re: [PATCH resend] MIPS: Allow FPU emulator to use non-stack area. On 10/07/2014 04:20 PM, Ralf Baechle wrote: > On Mon, Oct 06, 2014 at 02:18:19PM -0700, David Daney wrote: > >>> As an alternative, if the space of possible instruction with a delay >>> slot is sufficiently small, all such instructions could be mapped as >>> immutable code in a shared mapping, each at a fixed offset in the >>> mapping. I suspect this would be borderline-impractical (multiple >>> megabytes?), but it is the cleanest solution otherwise. >>> >> >> Yes, there are 2^32 possible instructions. Each one is 4 bytes, plus you >> need a way to exit after the instruction has executed, which would require >> another instruction. So you would need 32GB of memory to hold all those >> instructions, larger than the 32-bit virtual address space. > > Plus errata support for some older CPUs requires no other instructions > that might cause an exception to be present in the same cache line inflating > the size to 32 bytes per instruction. > > I've contemplated a full emulation - but that would require an emulator that > is capable of most of the instruction set. With all the random ASEs around > that would be hard to implement while the FPU emulator trampoline as currently > used has the advantage of automatically supporting ASEs, known and unknown. > So it's a huge bonus for maintenance. > Unfortunatly it breaks when our friends at Imgtec introduce their PC relative instructions in mipsr6, so an emulator may be unavoidable. David Daney -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists