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

trace perf event alloc #350

Merged

Conversation

sarahfujimori
Copy link
Contributor

This patch allows us to print information about the first step of the kprobe attach process, which is when a perf event is created. We do this by collecting kprobe function name, type, config, and probe offset from the perf_event arg of the function security_perf_event_alloc.

Signed-off-by: Sarah Fujimori [email protected]

@sarahfujimori sarahfujimori requested a review from a team as a code owner August 23, 2022 01:34
This patch allows us to print information about the first step of the kprobe attach process, which is when a perf event is created. We do this by collecting kprobe function name, type, config, and probe offset from the perf_event arg of the function security_perf_event_alloc.

Signed-off-by: Sarah Fujimori <[email protected]>
@sarahfujimori sarahfujimori force-pushed the pr/sarahfujimori/trace_perf_event_alloc branch from 9179466 to c20e145 Compare August 23, 2022 01:45
Copy link
Member

@tpapagian tpapagian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine, thanks! I believe that this is a good idea to add a unit-test for that (maybe in a follow-up PR).

@jrfastab jrfastab merged commit 6ffa22a into cilium:main Aug 24, 2022
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.

3 participants