kprobes is so excellent in performance analysis. But in many practical performance analysis scenarios, performance & debuging related configs maybe disabled. So, we should recompile the kernel for further analysis, this is not so convinient.
I've read this thread asked a question to use kprobes as a module (https://lkml.org/lkml/2012/5/15/46), and know the ftrace dependence issue. But when we meet a kernel compiled without CONFIG_KPROBES*, the only thing we need is the basic kprobes funtionality, have ftrace or not is not the major problem, in fact, most cases ftrace is disabled too. Do you have any advices on the conflicts between kernel hacking tools and practical kernel which compiled without it? If there is no kprobes module, what should we use? Signed-off-by: He Kuang <[email protected]> -- 1.7.9.5 -- 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/
