On Thu, Oct 01, 2026 at 11:14:36PM +0400, [email protected] wrote: > > The TraceEvent struct contains a "bool sstate" field which track whether > > a trace event was disabled statically. i.e. at build time via the > > "disable" property annotation in trace-events. > > > > The only runtime use of this field is to let "trace-event-get-state" > > report that an event is "unavailable" instead of reporting an error for > > an unknown trace event. > > > > Trace events are not ABI so their names can change and the event can > > come and go at any time. Thus there is little utility in reporting the > > existence of a disabled event that cannot ever be used at runtime. > > > > Removing the "bool sstate" field from TraceEvent saves 8 bytes of > > space in the struct, adding up to approx 64 KB across all current > > events. > > > > Signed-off-by: Daniel P. Berrangé <[email protected]> > > Message-ID: <[email protected]> > > Need a tracing.rst documentation update too.
I'll do that docs in the next patch, since that is the one that actually removes the functional part of the feature. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
