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!

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