User events — but not quite yet
User events — but not quite yet
Posted Apr 18, 2022 22:33 UTC (Mon) by pbonzini (subscriber, #60935)Parent article: User events — but not quite yet
All maintainers have a bad day every now and then, but this really looks like a bad example of kernel development.
Posted Apr 19, 2022 4:08 UTC (Tue)
by alison (subscriber, #63752)
[Link] (1 responses)
https://github.com/facebook/folly/tree/main/folly/tracing
Compiling against all of folly to get the userspace tracing would be a pain, but the code is Apache-licensed, so perhaps that is not necessary.
Posted Apr 20, 2022 6:27 UTC (Wed)
by lathiat (subscriber, #18567)
[Link]
This library generally is GPLv2-only licensed but the relevant sys/sdt.h file is "dedicated to the public domain, pursuant to CC0 (https://creativecommons.org/publicdomain/zero/1.0/)"
It uses the same definitions and is source-compatible with the definitions from DTRACE (so the macros are named DTRACE_*):
Posted Apr 20, 2022 8:05 UTC (Wed)
by net_benji (subscriber, #75195)
[Link]
> The whole user_events feature looks redundant to me.
User events — but not quite yet
User events — but not quite yet
https://sourceware.org/systemtap/wiki/AddingUserSpaceProb...
https://sourceware.org/systemtap/wiki/UserSpaceProbeImple...
User events — but not quite yet
https://lore.kernel.org/linux-trace-devel/CAADnVQJFjXDvqM...
> We have uprobes and usdt. It doesn't look to me that
> user_events provide anything new that wasn't available earlier.