seems like a good option if more bugs happen (inevitable)
I don't understand how the ability to profile userspace code with perf should have any interaction with drivers...
-
-
Remove whatever bogus interaction is there and the attack surface should disappear without breaking functionality.
-
yeah but what about other things perf interacts with that haven't yet been imagined either?
End of conversation
New conversation -
-
-
There are per-architecture/SoC drivers providing profiling support, and the feature set continues to grow.
-
Even the basic functionality is complex. It's not needed most of the time, so it's toggled off when unused.
-
How did they botch this? Base unpriv'd functionality should just be sampling user PC/SP at each interrupt.
-
It's way more complicated than that. It's a very generic interface for handling / filtering events, etc.
-
http://www.brendangregg.com/perf.html covers a bit of the functionality beyond the basics. It even has BPF integration.
-
It doesn't really have a defined scope. It's the API for exposing all kinds of event monitoring features.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.