-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Kernel locks tracing only in process context #5114
Comments
Currently BPF does not have helpers/kfuncs to identify the context. So I don't have a good way either. Is it possible that you filter some stack trace if their pattern suggests it is from non-process context? |
@yonghong-song There are patterns but if I filter lock acquisitions like this, I will be losing data on some locks. For example in stacks like these, I do not have separate stack traces giving me the name of the lock acquired by
I did manually add tracepoints/kfunc probes for some interrupt handlers like this:
But I do not think it's doing anything. Do you have any other suggestions? |
@yonghong-song Can you point me to any useful guide to create a helper function to access context? |
with libbpf the following works:
Then add your own on top:
|
Hi,
I am using an extended version of klockstat tool to trace spin locks but because of interrupts, the stack traces I am getting are quite messy. Ideally, I would like to trace only in the process context. Is there a way to do this in eBPF currently? I tried using
in_interrupt
but I do not think its supported. Can anyone suggest any workaround for this? Thanks in advance!The text was updated successfully, but these errors were encountered: