From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [lttng-dev] background information about LTTng timestamps
Date: Thu, 26 Jan 2012 15:19:23 -0500 [thread overview]
Message-ID: <20120126201923.GA27204@Krystal> (raw)
In-Reply-To: <20120126195151.GB14376@Krystal>
* Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
> * S?bastien Barth?l?my (barthelemy at crans.org) wrote:
> > I your aae88c703374f4b1fbb8a5e7e95591bf8ce3e837 commit you changed
> >
> > tsc_bits from 32 to 27 in liblttng-ust/ltt-ring-buffer-client.h
> >
> > Would not that alone have fixed the problem?
> > As explained in a previous email, I think, we were storing the bits
> > 32..64 instead of 27..59 in last_tsc.
> >
> > Thus missing 2**5 overflows.
> >
> > What do you think?
>
> I think it's almost certainly it. I'll let you know after some more
> testing.
Yep, tested and confirmed. I fixed both LTTng-modules and LTTng-UST
which had the same issue.
lttng-modules:
commit a2ef1c035ae3166f967113cb0ddec535465e694c
Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Date: Thu Jan 26 15:13:55 2012 -0500
Properly fix the timekeeping overflow detection
The underlying issue was a mismatch between the ring buffer
configuration description of the number of clock bits (32) saved and the
actual number used (27).
Introduce LTTNG_COMPACT_EVENT_BITS and LTTNG_COMPACT_TSC_BITS across the
code to remove all hardcoded instances of these values to ensure this
kind of mistake does not happen again.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Reported-by: S?bastien Barth?l?my <barthelemy at crans.org>
lttng-ust:
commit 79dfbf429c229ef733c5d8691a681edb91bee871
Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Date: Thu Jan 26 15:12:51 2012 -0500
Properly fix the timekeeping overflow detection
The underlying issue was a mismatch between the ring buffer
configuration description of the number of clock bits (32) saved and the
actual number used (27).
Introduce LTTNG_COMPACT_EVENT_BITS and LTTNG_COMPACT_TSC_BITS across the
code to remove all hardcoded instances of these values to ensure this
kind of mistake does not happen again.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Reported-by: S?bastien Barth?l?my <barthelemy at crans.org>
Thanks !
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2012-01-26 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPkDDd6Twa=k39RqACBGCAnFTvO=c+4-CPgg39NLCkNi+vwgzg@mail.gmail.com>
[not found] ` <20120109215551.GA23719@Krystal>
[not found] ` <CAPkDDd7KOYJ=TOELuzKBaCo=w3JCm4QNEAz4jzVLLkTt=JLFOw@mail.gmail.com>
[not found] ` <CAPkDDd5xDeBF+qOQdn7GpL-hHCVN-GaJojH0t_23nS5Xtgja=w@mail.gmail.com>
[not found] ` <CAPkDDd5EXRPXen3xmqZH11bwVCMU0WiH0W7OnhX6h=DrxejAww@mail.gmail.com>
2012-01-26 16:50 ` Mathieu Desnoyers
2012-01-26 18:18 ` Sébastien Barthélémy
2012-01-26 19:51 ` Mathieu Desnoyers
2012-01-26 20:19 ` Mathieu Desnoyers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120126201923.GA27204@Krystal \
--to=compudj@krystal.dyndns.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox