From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Bala Gundeboina <Bala.Gundeboina@kpit.com>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] profiling areas of LTTng
Date: Tue, 1 Aug 2023 15:10:05 -0400 [thread overview]
Message-ID: <2e581c21-6a85-2c2a-668c-8acdfd67a22d@efficios.com> (raw)
In-Reply-To: <MA0PR01MB6987337231830A85B736F2538505A@MA0PR01MB6987.INDPRD01.PROD.OUTLOOK.COM>
Hi Bala,
On 2023-07-31 07:01, Bala Gundeboina via lttng-dev wrote:
> Hi all,
> I are working in a Ti project, I already installed LTTng and i
> am able to trace userspace.I have a doubt regarding profiling areas of
> LTTng. In the project we are using ISP and RGB gstreamer. *can we
> profile exactly how much time taken by ISP and RGB gstreamer to process
> each frames* by using LTTng userspace tracing.
If the work being done to process each frame is being done via library
calls, it would be possible to use a custom userspace tracing helper
which instruments the necessary function calls, similar to those found
[here][1] which are loaded via LD_PRELOAD.
Otherwise you will need to modify and recompile your application to [add
tracepoints][2], or use a tool that does dynamic profiling.
> i want to know is this
> possible to profile by LTTng, what are the supported profiling areas and
> peripherals of LTTng, Sorry if any grammatical mistakes made.
>
It is possible to add static (user-defined) instrumentation to
applications using [liblttng-ust][3] in C/C++. [Helpers][4] are also
available for Java (JUL/Log4j) and Python applications.
Tracing of the linux kernel and various system information is possible
with kernel modules provided by [lttng-modules][5].
[1]: https://lttng.org/docs/v2.13/#doc-prebuilt-ust-helpers
[2]: https://lttng.org/docs/v2.13/#doc-c-application
[3]: https://lttng.org/docs/v2.13/#doc-lttng-ust
[4]: https://lttng.org/docs/v2.13/#doc-lttng-ust-agents
[5]: https://lttng.org/docs/v2.13/#doc-lttng-modules
thanks,
kienan
> Thanks & Regards
>
> Bala Gundeboina
> This message contains information that may be privileged or confidential
> and is the property of the KPIT Technologies Ltd. It is intended only
> for the person to whom it is addressed. If you are not the intended
> recipient, you are not authorized to read, print, retain copy,
> disseminate, distribute, or use this message or any part thereof. If you
> receive this message in error, please notify the sender immediately and
> delete all copies of this message. KPIT Technologies Ltd. does not
> accept any liability for virus infected mails.
>
> _______________________________________________
> 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
prev parent reply other threads:[~2023-08-01 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:01 Bala Gundeboina via lttng-dev
2023-08-01 19:10 ` Kienan Stewart via lttng-dev [this message]
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=2e581c21-6a85-2c2a-668c-8acdfd67a22d@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=Bala.Gundeboina@kpit.com \
--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