On Mon, 19 Apr 2021 11:08:04 +0300
Tzvetomir Stoyanov <tz.stoyanov@xxxxxxxxx> wrote:
> > We don't want all timestamps zero. We want to disable the starting event.
> >
> > By having this instead:
> >
> > } else {
> > tracecmd_warning("Timestamp %llu is before the initial offset %llu\n"
> > "\tSetting offset to 0",
> > ts, handle->tsc_calc.offset);
> > handle->tsc_calc.offset = 0;
> > ts = mul_u64_u32_shr(ts, handle->tsc_calc.mult, handle->tsc_calc.shift);
> > }
> >
>
> This will set the guest offset to 0, will not change the offsets of
> the other files. The result is that the files will not be displayed in
> sync, because of these few broken events. As this is only a sanity
> check, and should not happen if the patch "trace-cmd: Get the
> timestamp of the first recorded event as TSC offset" is applied, I
> would suggest to zero the broken timestamps and to advise the user to
> use "--raw-ts" option instead:
> "Timestamp %llu is before the initial offset %llu, set it to 0.
> Display the files with --raw-ts option to see the original
> timestamps.\n"
I still don't like it, because a thousand events all with the same
timestamp will still screw up everything (including the output of
kernelshark, as you'll see a thousand events at time zero, and then the
rest of the events at some way off in the future time).
And as this is in the library, having a warning is only applicable to
trace-cmd, and not any other user case.
Actually, I think we are looking at the wrong place to do the check. All
event streams (CPUs) need to be in monotonic order, or it's just corrupted
to begin with.
The library should supply a check to see if each stream starts after the
offset, and if not, give a report back to the user (trace-cmd in this case,
or kernelsharks ftrace plugin). Then give the user a way to give another
offset to tell all the other streams to convert to.
That is:
max = 0;
for each stream:
ret = read first event, compared to offset
if (!ret) {
/* ret will be how much off by offset */
if (ret > max)
max = ret;
}
if (max) {
for each stream:
Update offset by subtracting max
}
Look at each stream, and have some callback give you how much ahead the
first event is from its given offset. Take the biggest value from reading
all the streams, then tell all the streams to subtract its offset by that
max value. The end result is that all streams now start at a positive value.
-- Steve
|