From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Monitor user space threads without user events
Date: Mon, 15 Apr 2024 14:25:27 -0400 [thread overview]
Message-ID: <6e1feec7-7b25-4654-af4b-7ed942e4accb@efficios.com> (raw)
In-Reply-To: <CABRndgyC1hMY5vkJjBpPc_GSaSwCaDBc0KhmykOF4Sjthk_FLA@mail.gmail.com>
Hi Zvika,
with a session that has kernel events enabled, I think you could use the
sched_switch event.
thanks,
kienan
On 4/6/24 12:20 AM, Zvi Vered via lttng-dev wrote:
> Hello,
>
> My user space process contains 2 threads:
>
> First thread is blocked upon a kernel event created by a hardware
> interrupt handled by the kernel.
> The thread is sending ioctl which is blocked till this interrupt occurs.
>
> Second thread has just a 5msec sleep. It does something and then sleeps
> for 5msec. Forever.
>
> Is it possible to see when each thread is running (and not blocked or
> sleeps) ?
> I know how to do it with user events. I wonder if it's possible without
> any extra code.
>
> Thank you,
> Zvika
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2024-04-15 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 4:20 [lttng-dev] Monitor user space threads without user events Zvi Vered via lttng-dev
2024-04-15 18:25 ` Kienan Stewart via lttng-dev [this message]
2024-04-15 18:42 ` Zvi Vered 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=6e1feec7-7b25-4654-af4b-7ed942e4accb@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.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 read-only IMAP folder(s) and NNTP newsgroup(s).