Re: Unified tracing buffer

Sorry, probably lots of implicit assumptions in there that I forgot to explain

Ids for event types. Either allocated dynamically, if the tracer needs
new ids on each use, or statically assigned for others (like my fctrace
or Steven's ftrace, I believe). Should we have a reserved range / registry
for static allocation, maybe something like a very simple version of
devices.txt?

Sure, but it's per-tracer, so hopefully won't be a big problem (eg fctrace
would have a different event-id namespace from blktrace)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Unified tracing buffer
    ... Ids for event types. ... Either allocated dynamically, if the tracer needs ... Sure, but it's per-tracer, so hopefully won't be a big problem (eg fctrace ...
    (Linux-Kernel)
  • Re: Unified tracing buffer
    ... probably lots of implicit assumptions in there that I forgot to explain ... Ids for event types. ... Either allocated dynamically, if the tracer needs ...
    (Linux-Kernel)