From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Michael Jeanson <mjeanson@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] call trace while using lttng in petalinux 2019.2 (kernel 4.19)
Date: Wed, 16 Mar 2022 15:48:27 -0400 (EDT) [thread overview]
Message-ID: <1022626074.154650.1647460107562.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <ea1def8e-07af-9bc5-eb0b-7b2bfdb35f09@efficios.com>
----- On Mar 16, 2022, at 10:54 AM, lttng-dev lttng-dev@lists.lttng.org wrote:
> On 2022-03-16 09:25, Mathieu Desnoyers via lttng-dev wrote:
>> An alternative to query the lttng-modules version, if you really cannot
>> install modinfo, would
>> be:
>>
>> strings /lib/modules/$(uname -r)/extra/lttng-tracer.ko | grep "^version="
>
> Assuming a somewhat recent version of lttng-modules, the version will also be
> printed to dmesg when the modules are loaded.
This "LTTng: Loaded modules..." printk was added in v2.9.10 in the stable-2.9 branch of
lttng-modules. I suspect that the version of lttng-modules is even older here.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2022-03-16 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 6:48 [lttng-dev] call trace while using lttng in petalinux 2019.2 (kernel 4.19) GOLLAMUDI MADHAN MOHAN via lttng-dev
2022-03-15 15:49 ` Mathieu Desnoyers via lttng-dev
[not found] ` <CAB9=ZW6nDGJ+xv+6h4FHL2-63J9YE5P1KoAyvB+yWAx0rr46wA@mail.gmail.com>
2022-03-16 13:25 ` Mathieu Desnoyers via lttng-dev
2022-03-16 14:54 ` Michael Jeanson via lttng-dev
2022-03-16 19:48 ` Mathieu Desnoyers 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=1022626074.154650.1647460107562.JavaMail.zimbra@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mjeanson@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).