From: cpthk@hotmail.com (Jeffrey Chen)
Subject: [lttng-dev] LTTng event loglevel
Date: Mon, 22 Jun 2015 15:03:44 -0700 [thread overview]
Message-ID: <BLU169-W116D220BC28F5EEAB7D0DF8ABA10@phx.gbl> (raw)
In-Reply-To: <55887C23.8010306@voxpopuli.im>
Thanks for your answer.
I tried to use the TRACEPOINT_LOGLEVEL macro, but I was not able to make it working. I have my macro immediately follow my TRACE_EVENT macro "TRACEPOINT_LOGLEVEL(hello_world,my_first_tracepoint,TRACE_WARNING)"
I enabled the event with the --loglevel TRACE_WARNING parameter. When I run my code, and I do `lttng list --userspace`, I still get "hello_world:my_first_tracepoint (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)"
It looks like my code does not set the loglevel correctly, so it is still using the default loglevel. Am I doing anything wrong? Thanks.
> Date: Mon, 22 Jun 2015 17:20:35 -0400
> From: alexmonthy@voxpopuli.im
> To: cpthk at hotmail.com
> CC: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] LTTng event loglevel
>
> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150622/9383adc9/attachment.html>
prev parent reply other threads:[~2015-06-22 22:03 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
2015-06-22 22:03 ` Jeffrey Chen [this message]
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=BLU169-W116D220BC28F5EEAB7D0DF8ABA10@phx.gbl \
--to=cpthk@hotmail.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