From: munisekharrms@gmail.com (Muni Sekhar)
Subject: [lttng-dev] lttng view - doubt
Date: Thu, 11 Aug 2016 14:47:36 +0530 [thread overview]
Message-ID: <CAHhAz+gmqMC4ULLHgBwspYjdPJv_X8QGTMLLcifzgJvQvKAthg@mail.gmail.com> (raw)
In-Reply-To: <CA+jJMxsujC2iPpmjp6CcWYMVrD7owLG-zNBCfiRxpJVX+P7b+Q@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]
On Wed, Aug 10, 2016 at 12:41 AM, Jérémie Galarneau
<jeremie.galarneau at efficios.com> wrote:
> On Mon, Aug 8, 2016 at 2:37 AM, Muni Sekhar <munisekharrms at gmail.com> wrote:
>> [ Please keep me in CC as I'm not subscribed to the list]
>>
>>
>> Hello,
>>
>>
>> Few lines of lttng view trace about workqueue events:
>>
>> [11:07:08.208795325] (+0.000001677) testbox irq_handler_entry: {
>> cpu_id = 1 }, { irq = 16, name = "debug_irq" }
>>
>> [11:07:08.208822703] (+0.000027378) testbox workqueue_queue_work: {
>> cpu_id = 1 }, { work = 0xFFFF8801396D4F18, function =
>> 0xFFFFFFFFC07273B0, req_cpu = 256 }
>>
>> [11:07:08.208824380] (+0.000001677) testbox workqueue_activate_work: {
>> cpu_id = 1 }, { work = 0xFFFF8801396D4F18 }
>>
>> [11:07:08.208826615] (+0.000002235) testbox irq_handler_exit: { cpu_id
>> = 1 }, { irq = 16, ret = 1 }
>>
>> [11:07:08.208831364] (+0.000004749) testbox workqueue_execute_start: {
>> cpu_id = 1 }, { work = 0xFFFF8801396D4F18, function =
>> 0xFFFFFFFFC07273B0 }
>>
>> [11:07:08.208841422] (+0.000010058) testbox workqueue_execute_end: {
>> cpu_id = 1 }, { work = 0xFFFF8801396D4F18 }
>>
>>
>>
>>
>>
>> Can it be possible to print function name instead of ‘function =
>> 0xFFFFFFFFC07273B0’?
>
> Hi Muni,
>
> Unfortunately, you need to perform that look-up manually using
> addr2line or other such tools since Babeltrace (the viewer invoked by
> lttng view) only performs the address/symbol association for user
> space code. Extending that feature would be a great idea though!
Thanks for the reply. I used the /proc/kallsyms to fetch the symbol name.
>
> I'm CC-ing the Trace Compass mailing list; perhaps this is supported
> or already in the works.
>
> Thanks!
> Jérémie
>
>>
>> --
>> Thanks,
>> Sekhar
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>
> --
> Jérémie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
--
Thanks,
Sekhar
prev parent reply other threads:[~2016-08-11 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 6:37 Muni Sekhar
2016-08-09 19:11 ` Jérémie Galarneau
2016-08-11 9:17 ` Muni Sekhar [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=CAHhAz+gmqMC4ULLHgBwspYjdPJv_X8QGTMLLcifzgJvQvKAthg@mail.gmail.com \
--to=munisekharrms@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