From: Bala Gundeboina via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] profiling areas of LTTng
Date: Mon, 31 Jul 2023 11:01:26 +0000 [thread overview]
Message-ID: <MA0PR01MB6987337231830A85B736F2538505A@MA0PR01MB6987.INDPRD01.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1067 bytes --]
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. 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.
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.
[-- Attachment #1.2: Type: text/html, Size: 2162 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:[~2023-07-31 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:01 Bala Gundeboina via lttng-dev [this message]
2023-08-01 19:10 ` [lttng-dev] profiling areas of LTTng Kienan Stewart 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=MA0PR01MB6987337231830A85B736F2538505A@MA0PR01MB6987.INDPRD01.PROD.OUTLOOK.COM \
--to=lttng-dev@lists.lttng.org \
--cc=Bala.Gundeboina@kpit.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).