From: karim.yaghmour@opersys.com (Karim Yaghmour)
Subject: [lttng-dev] [RFC PATCH lttng-modules] LTTng logger ABI
Date: Mon, 17 Feb 2014 10:09:37 -0500 [thread overview]
Message-ID: <53022631.90209@opersys.com> (raw)
In-Reply-To: <1392502096-1900-1-git-send-email-mathieu.desnoyers@efficios.com>
That was quick :)
On 14-02-15 05:08 PM, Mathieu Desnoyers wrote:
> Add a user-space ABI (new file /proc/lttng-logger) to lttng-modules
> which can be written into by any user on the system. The content is
> saved into the kernel trace stream into the "lttng_logger" kernel event.
Nice. I think this would do for the use-case we discussed (i.e. feedback
Android's "ATRACE" events into lttng instead of ftrace's "trace_marker"
file.)
> The content of a single write is written into an lttng_logger event,
> provided the packet size is large enough to store the content. If it is
> not large enough, it won't be logged. However we cannot return any error
> to the caller, since there may be more than one trace session listening
> to this event.
Can we just truncate instead of dropping if the event is too large?
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
next prev parent reply other threads:[~2014-02-17 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 22:08 Mathieu Desnoyers
2014-02-17 15:09 ` Karim Yaghmour [this message]
2014-02-17 16:08 ` Mathieu Desnoyers
2014-02-17 16:13 ` Karim Yaghmour
2014-02-17 16:21 ` Mathieu Desnoyers
2014-02-17 16:26 ` Karim Yaghmour
2014-02-17 16:40 ` Mathieu Desnoyers
2014-02-17 16:41 ` Karim Yaghmour
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=53022631.90209@opersys.com \
--to=karim.yaghmour@opersys.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