From: francis.giraldeau@gmail.com (Francis Giraldeau)
Subject: [lttng-dev] make a trace_event in a modul (driver)
Date: Fri, 22 Nov 2013 14:07:59 -0500 [thread overview]
Message-ID: <528FAB8F.7040800@gmail.com> (raw)
In-Reply-To: <528F9561.3030802@gmx.de>
Le 2013-11-22 12:33, Klaus Dannecker a ?crit :
> Hi.
>
> Thank's J?r?mie!
>
> my account type is Administrator.
> sudo lttng list -k works good!
> how can I define a "tracing"group , so I no longer need the sudo command?
>
> another problem:
> i have add mycustomevents in the lttng_module like
> http://lists.lttng.org/pipermail/lttng-dev/2013-October/021540.html
> but after
> $ make
> $ sudo make modules_install
> $ sudo depmod -a
> and
> $ sudo lttng list -k
> my lttng-probe-mycustomevents.ko is now in
> /lib/modules/3.11.0-12-generic/extra/probes
> but i can't find my new event in the list!
On Ubuntu since kernel 3.8, modules are signed, and while unsigned
modules are loaded, if they contains tracepoints, they won't be
registered and won't be listed.
To avoid this inconvenience, a certificate x.509 must be generated and
modules signed with it, and the additional signing key must be loaded.
This process is not documented, but you can find the integration of this
process into the makefiles in lttng-modules addons.
https://github.com/giraldeau/lttng-modules/tree/addons
The module lttng-modsign is generated (look at the base makefile and
their code) and if they are loaded before your own module, tracepoints
tracepoints inside it should be registered correctly.
BTW, if you want, you can put your code directly under addons and start
your own tracepoints right away.
Cheers,
Francis
next prev parent reply other threads:[~2013-11-22 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 8:33 Klaus Dannecker
2013-11-13 17:37 ` Klaus Dannecker
2013-11-21 9:48 ` Klaus Dannecker
2013-11-21 15:49 ` Jérémie Galarneau
2013-11-21 16:42 ` Klaus Dannecker
2013-11-21 17:41 ` Jérémie Galarneau
2013-11-22 10:54 ` Klaus Dannecker
2013-11-22 16:12 ` Jérémie Galarneau
2013-11-22 17:33 ` Klaus Dannecker
2013-11-22 18:41 ` Jérémie Galarneau
2013-11-22 19:06 ` Jérémie Galarneau
2013-11-22 19:07 ` Francis Giraldeau [this message]
2013-11-22 18:54 Thibault, Daniel
2013-11-22 19:01 ` Jérémie Galarneau
2013-11-24 11:43 ` Klaus Dannecker
2013-11-24 16:01 ` Jérémie Galarneau
2013-11-24 18:26 ` Klaus Dannecker
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=528FAB8F.7040800@gmail.com \
--to=francis.giraldeau@gmail.com \
/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