trace: remove the TraceEventID and TraceEventVCPUID enums
The TraceEventID and TraceEventVCPUID enums constants are no longer actually used for anything critical. The TRACE_EVENT_COUNT limit is used to determine the size of the TraceEvents array, and can be removed if we just NULL terminate the array instead. The TRACE_VCPU_EVENT_COUNT limit is used as a magic value for marking non-vCPU events, and also for declaring the size of the trace dstate mask in the CPUState struct. The former usage can be replaced by a dedicated constant TRACE_EVENT_VCPU_NONE, defined as (uint32_t)-1. For the latter usage, we can simply define a constant for the number of VCPUs, avoiding the need for the full enum. The only other usages of the enum values can be replaced by accesing the id/vcpu_id fields via the named TraceEvent structs. Reviewed-by:Lluís Vilanova <vilanova@ac.upc.edu> Reviewed-by:
Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by:
Daniel P. Berrange <berrange@redhat.com> Message-id: 1475588159-30598-11-git-send-email-berrange@redhat.com Signed-off-by:
Stefan Hajnoczi <stefanha@redhat.com>
Showing
- scripts/tracetool/backend/simple.py 2 additions, 2 deletionsscripts/tracetool/backend/simple.py
- scripts/tracetool/format/events_c.py 11 additions, 5 deletionsscripts/tracetool/format/events_c.py
- scripts/tracetool/format/events_h.py 2 additions, 17 deletionsscripts/tracetool/format/events_h.py
- scripts/tracetool/format/h.py 1 addition, 2 deletionsscripts/tracetool/format/h.py
- trace/control-internal.h 10 additions, 9 deletionstrace/control-internal.h
- trace/control-target.c 1 addition, 1 deletiontrace/control-target.c
- trace/control.c 1 addition, 1 deletiontrace/control.c
- trace/control.h 9 additions, 23 deletionstrace/control.h
- trace/event-internal.h 6 additions, 0 deletionstrace/event-internal.h
- trace/simple.c 4 additions, 4 deletionstrace/simple.c
- trace/simple.h 1 addition, 1 deletiontrace/simple.h
Please register or sign in to comment