Removed the not so stable logic for tsc2nsec offset and replaced it with
trace-cmd library APIs which can be used from the library users to achieve
the same functionality.
These changes ignore the offset, part of the tsc2nsec data written in the
trace file metadata. Is it save to completely remove the offset field and to
break the format of this trace file option?
This is a RFC patchset, additional updates are required in case the changes
are approved:
- Update trace-cmd documentation.
- Remove offset field from tsc2nsec structures.
Tzvetomir Stoyanov (VMware) (5):
trace-cmd: Remove ts offset from tsc2nsec conversion
trace-cmd library: Remove useless check before applying ts offset
trace-cmd library: Store the timestamp of the first event when reading
a trace file
trace-cmd library: New API for modifyning the timestamp offset
trace-cmd report: New option --align-ts
include/trace-cmd/trace-cmd.h | 2 ++
lib/trace-cmd/trace-input.c | 39 ++++++++++++++++++++--
tracecmd/trace-read.c | 25 ++++++++++++--
tracecmd/trace-record.c | 62 -----------------------------------
tracecmd/trace-usage.c | 1 +
5 files changed, 61 insertions(+), 68 deletions(-)
--
2.30.2
|