| 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: <4C17B823.5070008@zytor.com> Date: Tue, 15 Jun 2010 10:28:03 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: David Miller <davem@...emloft.net> CC: jbaron@...hat.com, linux-kernel@...r.kernel.org, mingo@...e.hu, mathieu.desnoyers@...ymtl.ca, tglx@...utronix.de, rostedt@...dmis.org, andi@...stfloor.org, roland@...hat.com, rth@...hat.com, mhiramat@...hat.com, fweisbec@...il.com, avi@...hat.com, vgoyal@...hat.com, sam@...nborg.org Subject: Re: [PATCH 00/13] jump label v9 On 06/15/2010 10:13 AM, David Miller wrote: > From: Jason Baron <jbaron@...hat.com> > Date: Tue, 15 Jun 2010 10:28:11 -0400 > >> For example, the reason I have it in the code is b/c x86 determines >> the best no-op at run-time. Are other architectures going to have to >> require this kind of functionality. Or like sparc, are we going to >> be able to generally hard-code the nops on non-x86 at compile-time? > > I think most architectures will use a constant nop sequence, in fact > x86 is the only one I can think of that needs variable nop sequences. > One could potentially see that for other variable-length-instructions architectures, e.g. S390, m68k or ARM/Thumb2 as well. For fixed-length-instructions architectures, well, it shouldn't be an issue. -hpa -- 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