From: alexmonthy@voxpopuli.im (Alexandre Montplaisir)
Subject: [lttng-dev] LTTng event loglevel
Date: Mon, 22 Jun 2015 17:20:35 -0400 [thread overview]
Message-ID: <55887C23.8010306@voxpopuli.im> (raw)
In-Reply-To: <BLU169-W114739E6F78BF869CAD7B8ABA10@phx.gbl>
Hi,
On 2015-06-22 05:06 PM, Jeffrey Chen wrote:
> Hi:
>
> I am reading the LTTng and I am confused about the loglevel in the document. The document talked about it could assign a loglevel to each event. (http://lttng.org/docs/#doc-assigning-log-levels)
This part refers to when you define your own tracepoints in your pogram,
using the TRACEPOINT_EVENT macro.
> But, later in the document, it says all events from LTTng are traced as loglevel TRACE_DEBUG_FUNCTION. (http://lttng.org/docs/#doc-liblttng%E2%80%91ust%E2%80%91cyg%E2%80%91profile)
That part however, refers to using the liblttng-ust-cyg-profile library,
to automatically instrument function entries and exits. This library
implements the callbacks expected by cyg-profile, and puts the
information into UST tracepoints. Since it's this
liblttng-ust-cyg-profile library that "defines" the tracepoints here,
they are stuck at the log level specified in their definition, which is
TRACE_DEBUG_FUNCTION in this case.
Hope this helps,
Alexandre
next prev parent reply other threads:[~2015-06-22 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 21:06 Jeffrey Chen
2015-06-22 21:20 ` Alexandre Montplaisir [this message]
2015-06-22 22:03 ` Jeffrey Chen
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=55887C23.8010306@voxpopuli.im \
--to=alexmonthy@voxpopuli.im \
/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