Hi, Following Andi Kleen's advice, I splitted the jump-over-call into a speparate piece of infrastructure so it can be used more widely.
It also use a hash table to permit cond_call enable/disable both when the cond_call is armed and when a module containing an armed cond_call is loaded. Please add at the end of the 2.6.22-mm1 series, conditional-calls-architecture-independent-code.patch conditional-calls-hash-table.patch conditional-calls-non-optimized-architectures.patch conditional-calls-kconfig-menus.patch conditional-calls-i386-optimization.patch conditional-calls-powerpc-optimization.patch conditional-calls-documentation.patch # f00f-bug-use-cond-calls.patch profiling-use-cond-calls.patch Mathieu -- Mathieu Desnoyers Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/