All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: lttng trace format
       [not found] <CAPxN80Awz15=dY4vGGV0rHf_GM79uooPhYA8JOjV8Wp6jSBARQ@mail.gmail.com>
@ 2014-02-21  2:28 ` Jérémie Galarneau
       [not found] ` <CA+jJMxvMh6__mqNyoMUQRg1NzGssvzxVH4Pec4OzUcTzR0dtiQ@mail.gmail.com>
  1 sibling, 0 replies; 4+ messages in thread
From: Jérémie Galarneau @ 2014-02-21  2:28 UTC (permalink / raw)
  To: Jessica Foest; +Cc: lttng-dev, lttng-dev-request

On Thu, Feb 20, 2014 at 9:15 PM, Jessica Foest <jessica.foest@gmail.com> wrote:
> Hi all
> is there a document that explain the meaning of fields displayed in the
> traces generated by babeltrace ?
>
>
> an example :
>
> [19:52:06.617756425] (+0.000001667) workstation sys_splice: { cpu_id = 3 },
> { perf_branches = 418157709, perf_branch_instructions = 418156946,
> perf_cache_misses = 6682769, perf_cache_references = 50147680,
> perf_instructions = 3049323811, vppid = 587, ppid = 587, vtid = 3502, tid =
> 3502, vpid = 3499, nice = 0, prio = 20, procname = "lttng-consumerd", pid =
> 3499 }, { fd_in = 10, off_in = 0x0, fd_out = 26, off_out = 0x0, len = 65536,
> flags = 5 }
>
> the field mentioned in blue , is it the execution time of sys_splice ?
>

Hi Jessica,

It represents the delta between this event and the one before.

For instance, picking two events from a kernel trace on my system...

[21:25:29.901647477] (+0.000001585) XThink power_cpu_idle: { cpu_id =
2 }, { state = 4, cpu_id = 2 }
[21:25:29.901648940] (+0.000001463) XThink sched_stat_sleep: { cpu_id
= 6 }, { comm = "clementine", tid = 4318, delay = 5158461 }

901648940 - 901647477 = +0.000001463

Regards,
Jérémie

> if yes , what's the necessity of sys_exit ?
> Regards
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>



-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: lttng trace format
       [not found] ` <CA+jJMxvMh6__mqNyoMUQRg1NzGssvzxVH4Pec4OzUcTzR0dtiQ@mail.gmail.com>
@ 2014-02-21  2:57   ` Jessica Foest
  0 siblings, 0 replies; 4+ messages in thread
From: Jessica Foest @ 2014-02-21  2:57 UTC (permalink / raw)
  To: Jérémie Galarneau; +Cc: lttng-dev, lttng-dev-request


[-- Attachment #1.1: Type: text/plain, Size: 1739 bytes --]

Thanks a lot.


2014-02-20 21:28 GMT-05:00 Jérémie Galarneau <jeremie.galarneau@efficios.com
>:

> On Thu, Feb 20, 2014 at 9:15 PM, Jessica Foest <jessica.foest@gmail.com>
> wrote:
> > Hi all
> > is there a document that explain the meaning of fields displayed in the
> > traces generated by babeltrace ?
> >
> >
> > an example :
> >
> > [19:52:06.617756425] (+0.000001667) workstation sys_splice: { cpu_id = 3
> },
> > { perf_branches = 418157709, perf_branch_instructions = 418156946,
> > perf_cache_misses = 6682769, perf_cache_references = 50147680,
> > perf_instructions = 3049323811, vppid = 587, ppid = 587, vtid = 3502,
> tid =
> > 3502, vpid = 3499, nice = 0, prio = 20, procname = "lttng-consumerd",
> pid =
> > 3499 }, { fd_in = 10, off_in = 0x0, fd_out = 26, off_out = 0x0, len =
> 65536,
> > flags = 5 }
> >
> > the field mentioned in blue , is it the execution time of sys_splice ?
> >
>
> Hi Jessica,
>
> It represents the delta between this event and the one before.
>
> For instance, picking two events from a kernel trace on my system...
>
> [21:25:29.901647477] (+0.000001585) XThink power_cpu_idle: { cpu_id =
> 2 }, { state = 4, cpu_id = 2 }
> [21:25:29.901648940] (+0.000001463) XThink sched_stat_sleep: { cpu_id
> = 6 }, { comm = "clementine", tid = 4318, delay = 5158461 }
>
> 901648940 - 901647477 = +0.000001463
>
> Regards,
> Jérémie
>
> > if yes , what's the necessity of sys_exit ?
> > Regards
> >
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev@lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> >
>
>
>
> --
> Jérémie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
>

[-- Attachment #1.2: Type: text/html, Size: 2600 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: lttng trace format
@ 2014-02-21 13:19 Thibault, Daniel
  0 siblings, 0 replies; 4+ messages in thread
From: Thibault, Daniel @ 2014-02-21 13:19 UTC (permalink / raw)
  To: lttng-dev

> Date: Thu, 20 Feb 2014 21:15:42 -0500
> From: Jessica Foest <jessica.foest@gmail.com>
>
> is there a document that explain the meaning of fields displayed in the traces generated by babeltrace ?
>
> an example :
>
> [19:52:06.617756425] *(+0.000001667)* workstation sys_splice: { cpu_id = 3
}, { perf_branches = 418157709, perf_branch_instructions = 418156946,
perf_cache_misses = 6682769, perf_cache_references = 50147680,
perf_instructions = 3049323811, vppid = 587, ppid = 587, vtid = 3502, tid =
3502, vpid = 3499, nice = 0, prio = 20, procname = "lttng-consumerd", pid =
3499 }, { fd_in = 10, off_in = 0x0, fd_out = 26, off_out = 0x0, len =
65536, flags = 5 }
>
> the field mentioned in blue , is it the execution time of sys_splice ?
>
> if yes , what's the necessity of sys_exit ?

   Nothing in blue in the digest version of your post, sadly.  If you mean the *(+0.000001667)* field, that's just the time elapsed since the previous event.

Daniel U. Thibault
Protection des systèmes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber sécurité pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la défense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Québec QC  G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* lttng trace format
@ 2014-02-21  2:15 Jessica Foest
  0 siblings, 0 replies; 4+ messages in thread
From: Jessica Foest @ 2014-02-21  2:15 UTC (permalink / raw)
  To: lttng-dev, lttng-dev-request


[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]

Hi all
is there a document that explain the meaning of fields displayed in the
traces generated by babeltrace ?


an example :

[19:52:06.617756425] *(+0.000001667)* workstation sys_splice: { cpu_id = 3
}, { perf_branches = 418157709, perf_branch_instructions = 418156946,
perf_cache_misses = 6682769, perf_cache_references = 50147680,
perf_instructions = 3049323811, vppid = 587, ppid = 587, vtid = 3502, tid =
3502, vpid = 3499, nice = 0, prio = 20, procname = "lttng-consumerd", pid =
3499 }, { fd_in = 10, off_in = 0x0, fd_out = 26, off_out = 0x0, len =
65536, flags = 5 }

the field mentioned in blue , is it the execution time of sys_splice ?

if yes , what's the necessity of sys_exit ?
Regards

[-- Attachment #1.2: Type: text/html, Size: 907 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-02-21 13:19 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAPxN80Awz15=dY4vGGV0rHf_GM79uooPhYA8JOjV8Wp6jSBARQ@mail.gmail.com>
2014-02-21  2:28 ` lttng trace format Jérémie Galarneau
     [not found] ` <CA+jJMxvMh6__mqNyoMUQRg1NzGssvzxVH4Pec4OzUcTzR0dtiQ@mail.gmail.com>
2014-02-21  2:57   ` Jessica Foest
2014-02-21 13:19 Thibault, Daniel
  -- strict thread matches above, loose matches on Subject: below --
2014-02-21  2:15 Jessica Foest

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.