Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support automatic kprobe event detection in common case #194

Merged
merged 1 commit into from
Sep 9, 2015
Merged

Conversation

drzaeus77
Copy link
Collaborator

  • In the simple case, a user only creates 1 C function to be used with
    kprobes. Detect this common case and don't require the user to repeat
    themselves by passing the fn_name to attach_kprobe().
    e.g.: BPF(text='int sys_clone(void _ctx) {/_do stuff*/}').trace_print()

Signed-off-by: Brenden Blanco bblanco@plumgrid.com

* In the simple case, a user only creates 1 C function to be used with
  kprobes. Detect this common case and don't require the user to repeat
  themselves by passing the fn_name to attach_kprobe().
  e.g.: BPF(text='int sys_clone(void *ctx) {/*do stuff*/}').trace_print()

Signed-off-by: Brenden Blanco <bblanco@plumgrid.com>
4ast pushed a commit that referenced this pull request Sep 9, 2015
Support automatic kprobe event detection in common case
@4ast 4ast merged commit f63f35b into master Sep 9, 2015
@brendangregg
Copy link
Member

That's great, thanks, but as soon as people start doing this with 1 function, they'll likely expect 2 and more to work as well, if the C function name matches something from /sys/kernel/debug/tracing/available_filter_functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants