From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] make a trace_event in a module (driver)
Date: Mon, 25 Nov 2013 19:22:44 +0000 [thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD267A5E6B@VAL-E-01.valcartier.drdc-rddc.gc.ca> (raw)
> Date: Mon, 25 Nov 2013 12:00:14 -0500
> From: J?r?mie Galarneau <jeremie.galarneau@efficios.com>
>> Aha! There is one crucial mistake in the ibm.com document: he installs the packages in the wrong order. lttng-tools must be installed AFTER lttng-modules and lttng-ust. lttng-modules can be installed before, during or after lttng-ust, but userspace-rcu must be installed before lttng-ust.
>> The problem is that the configure of lttng-tools detects the presence or absence of lttng-modules and also detects the presence or absence of lttng-ust, and adjusts to both. By installing lttng-tools before lttng-modules, you've built an lttng-tools set that CANNOT be used to trace the kernel.
>>
>> So, try again from scratch, making sure to install lttng-tools last.
>
> lttng-tools checks for kernel modules at run time, not at configure time. You can safely install lttng-modules after lttng-tools and still use kernel tracing.
>
> Regards,
> J?r?mie
Dang, you're right. The build of lttng-tools reacts to the presence or absence of lttng-ust, but is indifferent to the presence or absence of lttng-modules. (Only liblttng-ctl.a is different, probably some internal timestamps or some such)
> klaus at ubuntu:~$ sudo lttng -vvv start
> DEBUG2 [2854/2854]: Config file path found: /home/klaus (in get_session_name() at utils.c:57)
> DEBUG1 [2854/2854]: Session name found: auto-20131124-091639 (in get_session_name() at utils.c:58)
> DEBUG1 [2854/2854]: Starting tracing for session auto-20131124-091639 (in start_tracing() at commands/start.c:81)
> DEBUG1 [2854/2854]: LSM cmd type : 16 (in send_session_msg() at lttng-ctl.c:131)
> 'ctrl c'
> klaus at ubuntu:~$
Let's try to identify the module responsible. First, make sure lttng-sessiond is NOT running. Then, do this in one shell:
$ sudo -H lttng-sessiond -vvv
It should fail after loading one of the modules.
You can also try:
$ sudo -H lttng-sessiond -vvv --no-kernel
In which case you should be able to do any lttng command except those involving the kernel. For example, 'lttng list -u'.
Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>
next reply other threads:[~2013-11-25 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:22 Thibault, Daniel [this message]
2013-11-26 17:32 ` Klaus Dannecker
-- strict thread matches above, loose matches on Subject: below --
2013-11-25 15:53 Thibault, Daniel
2013-11-25 17:00 ` Jérémie Galarneau
2013-11-25 18:14 ` Klaus Dannecker
2013-11-21 14:23 Thibault, Daniel
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=48CF5AC71E61DB46B70D0F388054EFFD267A5E6B@VAL-E-01.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/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