Stefan Hajnoczi d6b76d6805 trace: use static event ID mapping in simpletrace.stp ... This is a partial revert of commit 7f1b588f20 ("trace: emit name <-> ID mapping in simpletrace header"), which broke the SystemTap flight recorder because event mapping records may not be present in the ring buffer when the trace is analyzed. This means simpletrace.py --no-header does not know the event ID mapping needed to pretty-print the trace. Instead of numbering events dynamically, use a static event ID mapping as dictated by the event order in the trace-events-all file. The simpletrace.py script also uses trace-events-all so the next patch will fix the simpletrace.py --no-header option to take advantage of this knowledge. Cc: Daniel P. Berrange <berrange@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Daniel P. Berrange <berrange@redhat.com> Message-id: 20170815084430.7128-2-stefanha@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>		2017-08-15 12:50:29 +01:00
..
backend	trace: add TRACE_<event>_BACKEND_DSTATE()	2017-08-01 12:07:48 +01:00
format	trace: use static event ID mapping in simpletrace.stp	2017-08-15 12:50:29 +01:00
__init__.py	trace: add TRACE_<event>_BACKEND_DSTATE()	2017-08-01 12:07:48 +01:00
transform.py	trace: Add 'vcpu' event property to trace guest vCPU	2016-03-01 13:27:10 +00:00
vcpu.py	trace: Add 'vcpu' event property to trace guest vCPU	2016-03-01 13:27:10 +00:00