qemu/scripts/tracetool/backend
Daniel P. Berrange 80dd5c4918 trace: introduce a formal group name for trace events
The declarations in the generated-tracers.h file are
assuming there's only ever going to be one instance
of this header, as they are not namespaced. When we
have one header per event group, if a single source
file needs to include multiple sets of trace events,
the symbols will all clash.

This change thus introduces a '--group NAME' arg to the
'tracetool' program. This will cause all the symbols in
the generated header files to be given a unique namespace.

If no group is given, the group name 'common' is used,
which is suitable for the current usage where there is
only one global trace-events file used for code generation.

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Reviewed-by: Lluís Vilanova <vilanova@ac.upc.edu>
Message-id: 1475588159-30598-21-git-send-email-berrange@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2016-10-12 09:54:53 +02:00
..
__init__.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00
dtrace.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00
ftrace.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00
log.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00
simple.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00
syslog.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00
ust.py trace: introduce a formal group name for trace events 2016-10-12 09:54:53 +02:00