Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Erica Bugden via lttng-dev <lttng-dev@lists.lttng.org>
To: Zvi Vered <veredz72@gmail.com>, Christopher Harvey <chris@cwharvey.ca>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Lttng: display active threads in multiple cores.
Date: Tue, 2 Apr 2024 10:11:13 -0400	[thread overview]
Message-ID: <5d588684-17f3-4b96-aafd-9ff6728b2ddd@efficios.com> (raw)
In-Reply-To: <CABRndgy8RJ-rkszYGpvnqJ6oth35ajJhWgF8T4aWFEFjZiBz0g@mail.gmail.com>

Hello Zvika,

On 2024-03-29 01:09, Zvi Vered via lttng-dev wrote:
> Hi Christopher,
> 
> Thank you very much for your reply.
> Can you please explain what do you mean by ftrace-enabled kernel ?

I believe what Christopher means by "ftrace-enabled" kernel is that the 
Linux kernel has been configured to include ftrace. Both the ftrace 
tracer and the LTTng tracer use the same kernel tracepoints to extract 
execution information and these tracepoints are included in the kernel 
if ftrace is included.

Most Linux distributions will include ftrace by default. However, you 
can check whether this is the case by searching for `tracefs` in 
`/proc/filesystems` (assuming it's already mounted) or by trying to 
mount `tracefs`. `tracefs` is the filesystem ftrace uses to communicate 
with users.

More details about how to check if ftrace is enabled and how to enable 
it if not: 
https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/ftrace

The "More Information" section points to the primary sources (Linux 
kernel documentation), but I find this page to be a good starting point.

Best,
Erica

> 
> Best regards,
> Zvika
> 
> On Wed, Mar 27, 2024 at 7:32 PM Christopher Harvey via lttng-dev 
> <lttng-dev@lists.lttng.org <mailto:lttng-dev@lists.lttng.org>> wrote:
> 
>     you can use an ftrace-enabled kernel with lttng (maybe even just
>     tracecompass) or perfetto to get that kind of trace
> 
>     https://archive.eclipse.org/tracecompass.incubator/doc/org.eclipse.tracecompass.incubator.ftrace.doc.user/User-Guide.html <https://archive.eclipse.org/tracecompass.incubator/doc/org.eclipse.tracecompass.incubator.ftrace.doc.user/User-Guide.html>
> 
>     or
> 
>     https://ui.perfetto.dev/ <https://ui.perfetto.dev/>
> 
>     On Wed, Mar 27, 2024, at 5:26 AM, Zvi Vered via lttng-dev wrote:
>      > Hello,
>      >
>      > I have an application with 4 threads.
>      > I'm required to display on the graph when thread starts working
>     till it
>      > blocks for the next semaphore.
>      >
>      > But without using the lttng userspace library.
>      >
>      > Is it possible ?
>      >
>      > Thank you,
>      > Zvika
>      > _______________________________________________
>      > lttng-dev mailing list
>      > lttng-dev@lists.lttng.org <mailto: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>
>     _______________________________________________
>     lttng-dev mailing list
>     lttng-dev@lists.lttng.org <mailto: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>
> 
> 
> _______________________________________________
> 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

  reply	other threads:[~2024-04-02 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  9:26 Zvi Vered via lttng-dev
2024-03-27 17:28 ` Christopher Harvey via lttng-dev
2024-03-29  5:09   ` Zvi Vered via lttng-dev
2024-04-02 14:11     ` Erica Bugden via lttng-dev [this message]
2024-04-03  3:52       ` Zvi Vered via lttng-dev
2024-04-03 18:41         ` Erica Bugden 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=5d588684-17f3-4b96-aafd-9ff6728b2ddd@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=chris@cwharvey.ca \
    --cc=ebugden@efficios.com \
    --cc=veredz72@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