From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng 0.47 and LTTV 0.11.4 saves event lost count in the subbuffer header
Date: Mon, 27 Oct 2008 17:40:10 -0400 [thread overview]
Message-ID: <20081027214010.GA1246@Krystal> (raw)
Hi,
I just released lttng 0.47 and lttv 0.11.4 which updates the trace
format to 2.2. There are two new fields in the subbuffer header :
lost_events and number of subbuffers corrupted so far for the specific
subbuffer. Note that those fields are 32 bits wide and may overflow.
LTTV prints warnings such as this when it encounters a trace with
corrupted subbuffers or lost events :
WARNING **: 170459 events lost so far in tracefile /tmp/trace/cpu_1 at block 76
If you encounter this, you will probably want to make your subbuffers
larger (see lttctl --help), keep the workload smaller or use the flight
recorder mode.
Before, users had to check for dmesg output after taking the trace to
see if there were events lost, which was somewhat inconvenient.
This new LTTng version also add new specialized trap/fault probes.
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
reply other threads:[~2008-10-27 21:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081027214010.GA1246@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