Re: Re: [PATCH] kprobe: initialize kprobe_blacklist when it is used firstly

2013-04-02 Thread Masami Hiramatsu
(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 significan

Re: [PATCH] kprobe: initialize kprobe_blacklist when it is used firstly

2013-04-02 Thread oskar.andero
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_KPROBE

Re: [PATCH] kprobe: initialize kprobe_blacklist when it is used firstly

2013-04-02 Thread Masami Hiramatsu
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 funct

[PATCH] kprobe: initialize kprobe_blacklist when it is used firstly

2013-03-31 Thread Joonsoo Kim
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 p