Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "姜涛 Tao(AD)" <tao.jiang@jiduauto.com>,
	"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Need help: Kernel tracer not available and can't find the lttng-probe-latency_tracker
Date: Fri, 27 Oct 2023 13:47:21 -0400	[thread overview]
Message-ID: <bdef3e80-d299-40f7-8281-13d94fa21e5a@efficios.com> (raw)
In-Reply-To: <ZQZPR01MB10609C57DF7FA0C7CAF3AC6297DEA@ZQZPR01MB1060.CHNPR01.prod.partner.outlook.cn>

Hi Tao,

due to lack of financing, the latency_tracker project 
(https://github.com/efficios/latency-tracker/) isn't being actively 
maintained at this time.

Another option to get information on event latencies is to have 
"_entry"- and "_exit"-style events and perform post-processing of the 
traces with the Trace Compass Incubator "inandout" plugin.

https://git.eclipse.org/r/plugins/gitiles/tracecompass.incubator/org.eclipse.tracecompass.incubator/+/refs/heads/master/doc/org.eclipse.tracecompass.incubator.inandout.doc.user/doc/User-Guide.mediawiki

On 2023-10-25 02:41, 姜涛 Tao(AD) via lttng-dev wrote:
> Hi everyone, I have read this blog: 
> https://lttng.org/blog/2016/01/06/monitoring-realtime-latencies/ 
> <https://lttng.org/blog/2016/01/06/monitoring-realtime-latencies/>, and 
> I think latency_tracker project will be very useful in resovling my 
> problem under linux rt patch kernel 5.10, but it doesn't support linux 
> newer kernel, so I find the span-latency-tracker project later. But when 
> I use lttng create session,I get the error :
> Error: Event wakeup_latency: Kernel tracer not available (channel 
> channel0, session auto-20231024-134242)
> Error: Event block_latency: Kernel tracer not available (channel 
> channel0, session auto-20231024-134242)
> 
> 文本 描述已自动生成
> 
> And I find this tip: "To use the tracepoints provided by this module 
> with LTTng, you first have to connect LTTng probes to them. A patch 
> ready to be applied to the last lttng-modules is provided in extras/ 
> <https://github.com/adel-belkhiri/span-latency-tracker/blob/master/extras>. When installed, compiled, load the new probe module with modprobe lttng-probe-latency_tracker", but I can't find the "lttng-probe-latency_tracker" module in the lttng-module compiled modules or in the span-latency-tracker compiled modules.

This appears to be a fork of the latency_tracker project. We're not in a 
position to offer support for any changes that have been made there.

> 
> I also create the issue on the github: 
> https://github.com/adel-belkhiri/span-latency-tracker/issues/1 
> <https://github.com/adel-belkhiri/span-latency-tracker/issues/1>.
> Any help will be appreciated! Thanks!
> 
> 免责声明:本邮件所包含信息发给指定个人或机构,邮件可能包含保密或专属信 
> 息。未经接收者许可,不得阅读、转发或传播邮件内容,或根据邮件内容采取任何 
> 相关行动。如果错误地收到了此邮件,请与收件人联系并自行删除邮件内容。 
> Disclaimer:The information transmitted is intended only for the person 
> or entity to which it is addressed and may contain confidential and/or 
> privileged material. Any review, retransmission, dissemination or other 
> use of, or taking of any action in reliance upon, this information by 
> persons or entities other than the intended recipient is prohibited. If 
> you received this in error , please contact the sender and delete the 
> material from any computer.
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

thanks,
kienan

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

      reply	other threads:[~2023-10-27 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  6:41 姜涛 Tao(AD) via lttng-dev
2023-10-27 17:47 ` 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=bdef3e80-d299-40f7-8281-13d94fa21e5a@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=kstewart@efficios.com \
    --cc=tao.jiang@jiduauto.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