It is possible to enable two events having two different types but sharing the same name
(I'm not sure whether this issue is related to LTTng-tools or LTTng-modules, so I'm creating it under the LTTng umbrella project.)
It should be illegal to enable two events with different types sharing the same name.
This is possible right now (LTTng-tools 6b10b3b01eb754c0c3149490f700763dbac60ed5, LTTng-modules da0f6c58f715087f5091551070bf4350bf2768bf) in the kernel domain:
$ lttng enable-event -k sched_switch $ lttng enable-event -k --probe pci_iov_init sched_switch $ lttng list my-session ... Events: sched_switch (type: probe) [enabled] offset: 0x0 symbol: pci_iov_init sched_switch (loglevel: TRACE_EMERG (0)) (type: tracepoint) [enabled]
This would lead to two events named
sched_switch in the CTF metadata since tracepoint and dynamic probe events are not prefixed with an event type identifier.
However, what is observed is that the metadata only contains the tracepoint, not the dynamic probe. Also,
sched_switch tracepoint events are never recorded.
My recommandation is to disallow two events sharing the exact same name and parameters, except for the event type, within a given domain. UST does not have this problem now because the only available type is the tracepoint.
No data to display