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: Fri, 27 Feb 2015 22:32:39 +1030 From: Rusty Russell <rusty@...tcorp.com.au> To: Peter Zijlstra <peterz@...radead.org>, Andi Kleen <ak@...ux.intel.com> Cc: Andi Kleen <andi@...stfloor.org>, x86@...nel.org, linux-kernel@...r.kernel.org, mathieu.desnoyers@...icios.com, oleg@...hat.com, paulmck@...ux.vnet.ibm.com, mingo@...nel.org Subject: Re: [RFC][PATCH] module: Optimize __module_address() using a latched RB-tree Peter Zijlstra <peterz@...radead.org> writes: > One of the users of this is __kernel_text_address() which is employed in > many stack unwinders; which in turn are used by perf-callchain (possibly > from NMI context). Um, so the stack unwinders use "does this look like a kernel address" because we omit the frame pointer? To keep that optimization, we add 220 non-trivial lines to module.c? Don't get me wrong, it's cute code, but I do wonder if at some point a grown up is going to come along and tell us to stop :) Cheers, Rusty. -- 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