(2014/04/01 16:28), Jovi Zhangwei wrote:
> Note:
> Why ktap support 'kdebug.kprobe' and 'kdebug.tracepoint' when
> it already support perf backend event(trace xxx {})?
>
> Because benchmark shows raw kprobe and tracpoint interface is faster
> than perf backed tracing, nearl
On Tue, Apr 1, 2014 at 2:59 PM, Masami Hiramatsu
wrote:
> (2014/03/31 19:14), Jovi Zhangwei wrote:
>> On Mon, Mar 31, 2014 at 5:10 PM, Masami Hiramatsu
>> wrote:
>>> (2014/03/28 22:47), Jovi Zhangwei wrote:
kp_events.c handle ktap events management(registry, destroy, event
callback)
>>
(2014/03/31 19:14), Jovi Zhangwei wrote:
> On Mon, Mar 31, 2014 at 5:10 PM, Masami Hiramatsu
> wrote:
>> (2014/03/28 22:47), Jovi Zhangwei wrote:
>>> kp_events.c handle ktap events management(registry, destroy, event callback)
>>>
>>> This file is core event management interface between ktap and k
On Mon, Mar 31, 2014 at 5:10 PM, Masami Hiramatsu
wrote:
> (2014/03/28 22:47), Jovi Zhangwei wrote:
>> kp_events.c handle ktap events management(registry, destroy, event callback)
>>
>> This file is core event management interface between ktap and kernel.
>>
>> Exposed functions:
>> 1). kp_events_
(2014/03/28 22:47), Jovi Zhangwei wrote:
> kp_events.c handle ktap events management(registry, destroy, event callback)
>
> This file is core event management interface between ktap and kernel.
>
> Exposed functions:
> 1). kp_events_init/kp_events_exit
>
> 2). kp_event_create_kprobe
> cr
kp_events.c handle ktap events management(registry, destroy, event callback)
This file is core event management interface between ktap and kernel.
Exposed functions:
1). kp_events_init/kp_events_exit
2). kp_event_create_kprobe
create kprobe event, for example:
kdebug.kpro
6 matches
Mail list logo