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

consider supporting kernel trace data input #3

Open
ThinkOpenly opened this issue Mar 26, 2018 · 0 comments
Open

consider supporting kernel trace data input #3

ThinkOpenly opened this issue Mar 26, 2018 · 0 comments

Comments

@ThinkOpenly
Copy link
Contributor

Add support for parsing output from reading the kernel trace buffer (usually /sys/kernel/debug/tracing/trace). This is text-based:

 sshd-15165 [000] .... 4338237.604419: sys_enter: NR 142 (e, 1001a717b30, 1001a729ee0, 0, 0, 2008)
 sshd-15165 [000] d... 4338237.604424: sched_switch: prev_comm=sshd prev_pid=15165 prev_prio=120 prev_state=S ==> next_comm=swapper/0 next_pid=0 next_prio=120
 bash-15453 [004] .... 4338237.604655: sched_process_exec: filename=/bin/cat pid=15453 old_pid=15453
 bash-15453 [004] .... 4338237.604658: sys_exit: NR 0 = 0
 bash-15453 [004] .... 4338237.604690: sys_enter: NR 45 (0, 0, 3fff7d6b0000, 3fffe5aac332, 80, 3fff7d6f0680)
 bash-15453 [004] .... 4338237.604691: sys_exit: NR 45 = 1099686346752
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

No branches or pull requests

1 participant