From: Yonghong Yan via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: process/thread-specific UST tracing
Date: Fri, 15 May 2020 13:16:47 -0400 [thread overview]
Message-ID: <CACJEY85H4OMTz9ggfZZP3QCXoWgLiJgsMVNTP8LNBAF67mQTEQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 746 bytes --]
I am tracing a multiprocess/multithreaded code (MPI/OpenMP) using
lttng-ust. Right now, I need to include process id and thread id for each
event in order to generate process/thread indexed view of the traces. Is
there a way that I can store per-process events into a specific buffer
without mixing the events with other events that are generated on the same
CPU? The same thing for per-thread events, I would like lttng or CTF to
allow to store per-thread events in a specific buffer without mixing the
events with other events on the same CPU channel. With that feature, I do
not need to store process id and thread id in each event and then need to
query all the events in order to collect per-process or per-thread event.
Thank you
Yonghong
[-- Attachment #1.2: Type: text/html, Size: 1169 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
WARNING: multiple messages have this Message-ID (diff)
From: Yonghong Yan via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] process/thread-specific UST tracing
Date: Fri, 15 May 2020 13:16:47 -0400 [thread overview]
Message-ID: <CACJEY85H4OMTz9ggfZZP3QCXoWgLiJgsMVNTP8LNBAF67mQTEQ@mail.gmail.com> (raw)
Message-ID: <20200515171647.bEW6JBZcfxnOV5E896RFe3ZSl-2Crf8nyqXwvRhEfxE@z> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 746 bytes --]
I am tracing a multiprocess/multithreaded code (MPI/OpenMP) using
lttng-ust. Right now, I need to include process id and thread id for each
event in order to generate process/thread indexed view of the traces. Is
there a way that I can store per-process events into a specific buffer
without mixing the events with other events that are generated on the same
CPU? The same thing for per-thread events, I would like lttng or CTF to
allow to store per-thread events in a specific buffer without mixing the
events with other events on the same CPU channel. With that feature, I do
not need to store process id and thread id in each event and then need to
query all the events in order to collect per-process or per-thread event.
Thank you
Yonghong
[-- Attachment #1.2: Type: text/html, Size: 1169 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
next reply other threads:[~2020-05-15 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 17:16 Yonghong Yan via lttng-dev [this message]
2020-05-15 17:16 ` [lttng-dev] process/thread-specific UST tracing Yonghong Yan via lttng-dev
2020-05-15 19:15 ` Mathieu Desnoyers via lttng-dev
2020-05-15 19:15 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
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=CACJEY85H4OMTz9ggfZZP3QCXoWgLiJgsMVNTP8LNBAF67mQTEQ@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=yanyh15@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;
as well as URLs for NNTP newsgroup(s).