From: francis.giraldeau@gmail.com (Francis Giraldeau)
Subject: [lttng-dev] [PATCH] Expose kernel tracer to user-space
Date: Wed, 06 Jun 2012 01:40:33 +0200 [thread overview]
Message-ID: <4FCE98F1.4020803@gmail.com> (raw)
In-Reply-To: <1338938654-16515-1-git-send-email-francis.giraldeau@gmail.com>
Le 2012-06-06 01:24, Francis Giraldeau a ?crit :
> By writing to the file /proc/lttng, a user-space application creates a
> kernel event. The event's payload is by default UTF-8 text, but any data
> can be written, up to 1024 bytes. Null-character is optional and is not
> enforced. The event uses sequence for space efficiency and to store any
> data as payload.
>
> Update: split the probe code into it's own module and make it an optional
> feature of lttng-abi. The feature is enabled when the module is loaded. The
> lttng-abi module exports a register function and includes a wrapper for
> lttng_fops write. This is required since struct file_operations must be const.
> Since the module dependency is reversed, unloading the lttng-uevent module is
> done only when it's not used anymore. This is done with rwlock synchronisation.
> The synchronisation doesn't prevent starvation, but this situation is unlikely
> and can be prevented by stop active tracing sessions.
One little gotcha: after modprobe lttng-uevent, the module
lttng-probe-uevent must be loaded manually, otherwise lttng_uevent is
not listed with "lttng list -k". Is there a way to make the probe load
automatically when lttng-uevent is loaded?
Cheers,
Francis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4476 bytes
Desc: Signature cryptographique S/MIME
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120606/199bca17/attachment-0001.bin>
next prev parent reply other threads:[~2012-06-05 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 23:24 Francis Giraldeau
2012-06-05 23:40 ` Francis Giraldeau [this message]
2012-06-26 6:40 ` Mathieu Desnoyers
2012-06-26 14:52 ` Francis Giraldeau
2012-06-26 17:01 ` Mathieu Desnoyers
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=4FCE98F1.4020803@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