* Re: Adding thread timestamp to event context
[not found] <CADwgpi8Nvz4--8V16mU=GoQN5z9dUSvphuSQ3eOL3m0RVYxEeQ@mail.gmail.com>
@ 2018-10-25 13:02 ` Mathieu Desnoyers
[not found] ` <125123961.343.1540472537413.JavaMail.zimbra@efficios.com>
1 sibling, 0 replies; 4+ messages in thread
From: Mathieu Desnoyers @ 2018-10-25 13:02 UTC (permalink / raw)
To: Alok Priyadarshi; +Cc: lttng-dev
[-- Attachment #1.1: Type: text/plain, Size: 1310 bytes --]
----- On Oct 24, 2018, at 11:05 PM, Alok Priyadarshi <alokpr@gmail.com> wrote:
> I am trying to add a thread timestamp to trace events. By thread timestamp I
> mean the value returned by clock_gettime(CLOCK_THREAD_CPUTIME_ID):
> [ https://linux.die.net/man/3/clock_gettime |
> https://linux.die.net/man/3/clock_gettime ]
> I could do this by creating custom events, but I am wondering if there is
> already a way to add this information to event context. I have tried using the
> following arguments to lttng-add-context, but none of them add any additional
> information:
> perf:cpu:cpu-cycles
> perf:cpu:cycles
> perf:thread:cpu-cycles
> perf:thread:cycles
> Note that I have only enabled userspace events. I use the following sequence of
> commands to capture trace:
> lttng create
> lttng enable-event --userspace --all
> lttng add-context --userspace -t vpid -t vtid -t perf:thread:cycles
> lttng start
> lttng stop
We would need to extend lttng-ust implementation and lttng-tools to add those
additional contexts. It would make sense to add these.
Thanks,
Mathieu
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
[-- Attachment #1.2: Type: text/html, Size: 2497 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <125123961.343.1540472537413.JavaMail.zimbra@efficios.com>]
* Re: Adding thread timestamp to event context
[not found] ` <125123961.343.1540472537413.JavaMail.zimbra@efficios.com>
@ 2018-10-25 21:33 ` Alok Priyadarshi
[not found] ` <CADwgpi-d6gDUB4djoBu_Va-STEGu-2mLm_xfLH=FXb0cd9_O8A@mail.gmail.com>
1 sibling, 0 replies; 4+ messages in thread
From: Alok Priyadarshi @ 2018-10-25 21:33 UTC (permalink / raw)
To: Mathieu Desnoyers; +Cc: lttng-dev
[-- Attachment #1.1: Type: text/plain, Size: 1463 bytes --]
Thanks for your prompt response Mathieu. Can I expect this to happen
soonish?
On Thu, Oct 25, 2018 at 6:02 AM Mathieu Desnoyers <
mathieu.desnoyers@efficios.com> wrote:
> ----- On Oct 24, 2018, at 11:05 PM, Alok Priyadarshi <alokpr@gmail.com>
> wrote:
>
> I am trying to add a thread timestamp to trace events. By thread timestamp
> I mean the value returned by clock_gettime(CLOCK_THREAD_CPUTIME_ID):
> https://linux.die.net/man/3/clock_gettime
>
> I could do this by creating custom events, but I am wondering if there is
> already a way to add this information to event context. I have tried using
> the following arguments to lttng-add-context, but none of them add any
> additional information:
> perf:cpu:cpu-cycles
> perf:cpu:cycles
> perf:thread:cpu-cycles
> perf:thread:cycles
>
> Note that I have only enabled userspace events. I use the following
> sequence of commands to capture trace:
> lttng create
> lttng enable-event --userspace --all
> lttng add-context --userspace -t vpid -t vtid -t perf:thread:cycles
> lttng start
> lttng stop
>
> We would need to extend lttng-ust implementation and lttng-tools to add
> those
> additional contexts. It would make sense to add these.
>
> Thanks,
>
> Mathieu
>
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
>
[-- Attachment #1.2: Type: text/html, Size: 3275 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CADwgpi-d6gDUB4djoBu_Va-STEGu-2mLm_xfLH=FXb0cd9_O8A@mail.gmail.com>]
* Re: Adding thread timestamp to event context
[not found] ` <CADwgpi-d6gDUB4djoBu_Va-STEGu-2mLm_xfLH=FXb0cd9_O8A@mail.gmail.com>
@ 2018-10-26 9:49 ` Mathieu Desnoyers
0 siblings, 0 replies; 4+ messages in thread
From: Mathieu Desnoyers @ 2018-10-26 9:49 UTC (permalink / raw)
To: Alok Priyadarshi; +Cc: lttng-dev
[-- Attachment #1.1: Type: text/plain, Size: 2024 bytes --]
You are the first to show interest in this. It is not on our roadmap for the moment.
Thanks,
Mathieu
----- On Oct 25, 2018, at 10:33 PM, Alok Priyadarshi <alokpr@gmail.com> wrote:
> Thanks for your prompt response Mathieu. Can I expect this to happen soonish?
> On Thu, Oct 25, 2018 at 6:02 AM Mathieu Desnoyers < [
> mailto:mathieu.desnoyers@efficios.com | mathieu.desnoyers@efficios.com ] >
> wrote:
>> ----- On Oct 24, 2018, at 11:05 PM, Alok Priyadarshi < [ mailto:alokpr@gmail.com
>> | alokpr@gmail.com ] > wrote:
>>> I am trying to add a thread timestamp to trace events. By thread timestamp I
>>> mean the value returned by clock_gettime(CLOCK_THREAD_CPUTIME_ID):
>>> [ https://linux.die.net/man/3/clock_gettime |
>>> https://linux.die.net/man/3/clock_gettime ]
>>> I could do this by creating custom events, but I am wondering if there is
>>> already a way to add this information to event context. I have tried using the
>>> following arguments to lttng-add-context, but none of them add any additional
>>> information:
>>> perf:cpu:cpu-cycles
>>> perf:cpu:cycles
>>> perf:thread:cpu-cycles
>>> perf:thread:cycles
>>> Note that I have only enabled userspace events. I use the following sequence of
>>> commands to capture trace:
>>> lttng create
>>> lttng enable-event --userspace --all
>>> lttng add-context --userspace -t vpid -t vtid -t perf:thread:cycles
>>> lttng start
>>> lttng stop
>> We would need to extend lttng-ust implementation and lttng-tools to add those
>> additional contexts. It would make sense to add these.
>> Thanks,
>> Mathieu
>>> _______________________________________________
>>> lttng-dev mailing list
>>> [ mailto:lttng-dev@lists.lttng.org | lttng-dev@lists.lttng.org ]
>>> [ https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev |
>>> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev ]
>> --
>> Mathieu Desnoyers
>> EfficiOS Inc.
>> [ http://www.efficios.com/ | http://www.efficios.com ]
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
[-- Attachment #1.2: Type: text/html, Size: 4180 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
^ permalink raw reply [flat|nested] 4+ messages in thread
* Adding thread timestamp to event context
@ 2018-10-24 22:05 Alok Priyadarshi
0 siblings, 0 replies; 4+ messages in thread
From: Alok Priyadarshi @ 2018-10-24 22:05 UTC (permalink / raw)
To: lttng-dev
[-- Attachment #1.1: Type: text/plain, Size: 758 bytes --]
I am trying to add a thread timestamp to trace events. By thread timestamp
I mean the value returned by clock_gettime(CLOCK_THREAD_CPUTIME_ID):
https://linux.die.net/man/3/clock_gettime
I could do this by creating custom events, but I am wondering if there is
already a way to add this information to event context. I have tried using
the following arguments to lttng-add-context, but none of them add any
additional information:
perf:cpu:cpu-cycles
perf:cpu:cycles
perf:thread:cpu-cycles
perf:thread:cycles
Note that I have only enabled userspace events. I use the following
sequence of commands to capture trace:
lttng create
lttng enable-event --userspace --all
lttng add-context --userspace -t vpid -t vtid -t perf:thread:cycles
lttng start
lttng stop
[-- Attachment #1.2: Type: text/html, Size: 1037 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-10-26 9:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CADwgpi8Nvz4--8V16mU=GoQN5z9dUSvphuSQ3eOL3m0RVYxEeQ@mail.gmail.com>
2018-10-25 13:02 ` Adding thread timestamp to event context Mathieu Desnoyers
[not found] ` <125123961.343.1540472537413.JavaMail.zimbra@efficios.com>
2018-10-25 21:33 ` Alok Priyadarshi
[not found] ` <CADwgpi-d6gDUB4djoBu_Va-STEGu-2mLm_xfLH=FXb0cd9_O8A@mail.gmail.com>
2018-10-26 9:49 ` Mathieu Desnoyers
2018-10-24 22:05 Alok Priyadarshi
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.