Something that's always been an issue in the utrace interface is the
management of struct utrace_attached_engine. It's tricky that you have to
use RCU and/or follow picayune rules in the attach+set_events-callbacks
sequence to be sure your engine pointer is valid. From the beginning, I
expected
Roland McGrath wrote:
We've mentioned global tracing. I think it's time now to discuss it
thoroughly and decide what we do or don't want to do.
...
2. Why do we want utrace global tracing?
From a systemtap point of view, we'd certainly use global tracing.
...
3. What would it look like?
2. Why do we want utrace global tracing?
From a systemtap point of view, we'd certainly use global tracing.
You're using tracepoints/markers too. (You'll use anything, you minx.)
What we need is reasons for this to be a utrace feature.
Global tracing would be *really* nice; your reasons
