From: Zvi Vered via lttng-dev <lttng-dev@lists.lttng.org>
To: Kienan Stewart <kstewart@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] lttng-modules(13.9) : insmod order
Date: Wed, 3 Apr 2024 06:51:02 +0300 [thread overview]
Message-ID: <CABRndgzYjmfBYKsHsJ=fzi6c=24ey2gEdxpMn3e8Ly2EZJVA2Q@mail.gmail.com> (raw)
In-Reply-To: <7cc79ada-f8cb-49fc-aec8-4d0b5c9ba2bd@efficios.com>
[-- Attachment #1.1: Type: text/plain, Size: 1044 bytes --]
Hi Kienan,
Thank you for your help!
Best regards,
Zvika
On Tue, Apr 2, 2024 at 4:17 PM Kienan Stewart <kstewart@efficios.com> wrote:
> Hi Zvika,
>
> a sessiond launched as root will automatically try to load the
> appropriate kernel modules as mentioned here[1], using either modprobe
> or libkmod depending on how the build was configured.
>
> thanks,
> kienan
>
> [1]: https://lttng.org/docs/v2.13/#doc-lttng-modules
>
>
> On 3/30/24 10:52 PM, Zvi Vered via lttng-dev wrote:
> > Hello,
> >
> > For some reason, I failed to integrate v13.9 into buildroot 2023.02.2
> > But I compiled all modules with the my kernel source: 5.4.249
> >
> > Can you please tell what is the right order of *insmod *for the kernel
> > modules ?
> >
> > All I need is to record IRQ events and user space events.
> >
> > Thank you,
> > Zvika
> >
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev@lists.lttng.org
> > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
[-- Attachment #1.2: Type: text/html, Size: 1767 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
prev parent reply other threads:[~2024-04-03 3:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 2:52 [lttng-dev] lttng-modules(13.9) : insmod order Zvi Vered via lttng-dev
2024-04-02 13:17 ` Kienan Stewart via lttng-dev
2024-04-03 3:51 ` Zvi Vered 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='CABRndgzYjmfBYKsHsJ=fzi6c=24ey2gEdxpMn3e8Ly2EZJVA2Q@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).