(2013/04/02 21:16), oskar.and...@sonymobile.com wrote: > On 12:49 Tue 02 Apr , Masami Hiramatsu wrote: >> Hi, >> >> (2013/04/01 15:55), Joonsoo Kim wrote: >>> Currently, initializing kprobe_blacklist is done during boot process. >>> It takes 230 ms on our android platform and this is significant amount >>> for our use case. We can disable CONFIG_KPROBES for production kernel, >>> but it is hassle. This kprobe functionality is not commonly used, >>> so we don't need to pay this cost at all times. With this rationale, >>> change code to initialize kprobe_blacklist when it is used firstly. >> >> I saw similar patch from Oskar and Toby, and I decided to wait >> until his blacklist separating work. I'd like to ask Oskar >> how the patch is going first. >> > > I am currently preparing a series of 4 patches including the move of > blacklist initialization (same as Joonsoo's patch) and separation of > architecture specific blackpoints. > The patches are dependent, so I appreciate if you wait a bit. > > You can expect the series at latest tomorrow.
Thanks! I'd like to see such general solution :) Thank you, -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu...@hitachi.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
