| 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
| ||
|
Message-ID: <CACcUPpaCoDdOnmWxf0h4vJz-=SFDnOExiChVaJiqce+_204+2Q@mail.gmail.com> Date: Wed, 25 Jan 2012 13:26:02 +0100 From: Stefan Seidel <stefans@...roid-x86.org> To: linux-kernel@...r.kernel.org Cc: Mikael Pettersson <mikpe@...uu.se> Subject: Re: Emulating unsupported x86 opcodes in software On Wed, Jan 25, 2012 at 13:17, Mikael Pettersson <mikpe@...uu.se> wrote: > Just two general comments, not specifically related to emulating SSE3: > > 1. Deploying the emulator from userspace would be preferable. LD_PRELOAD a > library containing the SSE3 emulation and init code to set up a SIGILL > handler. This solves all the ring 0 vs 3 problems and avoids needing > any kernel modifications. Thanks for the hint. I knew that this would be a possiblity, but I don't think it's wise or possible to run _every_ binary that could possibly be started on the machine with this technique - hence the kernel integration. > 2. It's not always the case that new instructions in later generation x86 > processors trap in earlier generation processors. E.g., several years I think that's not a problem in the processor generation I target. The said emulation has been used successfully on a lot of machines running MacOS X, and this included the use of heavy multi-media apps which actually use these intructions a lot. Stefan -- 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