tracing: Unbreak user events

The user events was added a bit prematurely, and there were a few kernel
developers that had issues with it. The API also needed a bit of work to
make sure it would be stable. It was decided to make user events "broken"
until this was settled. Now it has a new API that appears to be as stable
as it will be without the use of a crystal ball. It's being used within
Microsoft as is, which means the API has had some testing in real world
use cases. It went through many discussions in the bi-weekly tracing
meetings, and there's been no more comments about updates.

I feel this is good to go.

Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: default avatarSteven Rostedt (Google) <rostedt@goodmis.org>
parent 4bec284c
...@@ -792,7 +792,6 @@ config USER_EVENTS ...@@ -792,7 +792,6 @@ config USER_EVENTS
bool "User trace events" bool "User trace events"
select TRACING select TRACING
select DYNAMIC_EVENTS select DYNAMIC_EVENTS
depends on BROKEN || COMPILE_TEST # API needs to be straighten out
help help
User trace events are user-defined trace events that User trace events are user-defined trace events that
can be used like an existing kernel trace event. User trace can be used like an existing kernel trace event. User trace
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment