Skip to content

Add General Support for BTF and CTF in OneCollect / record-trace #215

Description

@mscacarden

Need ability to write more portable record-trace scripts and OneCollect programs without the need for determining addresses, offsets, and data types by hand as these are fragile ranging from one machine to the next, one kernel to the next, and one architecture to the next.

This would allow the portable use of kprobes and uprobes.

An example of these would be:

event_from_kprobe_btf("netmon","tcp_change_state","tcp_set_state","family=sk->__sk_common.skc_family) instead of event_from_kprobe("netmon","tcp_change_state","tcp_set_state","family=+0x10(%di):u16)

and

event_from_uprobe_ctf("memmon","uprobe_alloc", "/lib/libc.so.6", "libc_malloc", "size=size") instead of event_from_uprobe("memmon","uprobe_alloc", "/lib/libc.so.6", "libc_malloc+0x240", "size=%di:u64")

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions