From: Lin ArcX via lttng-dev <lttng-dev@lists.lttng.org>
To: Kienan Stewart <kstewart@efficios.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Can't receive a lot of functions that i registerd as trace-points
Date: Wed, 25 Oct 2023 10:54:07 +0200 [thread overview]
Message-ID: <CALBKf8JHM1xDf9L3m+4p-2eNQ2s6yGJw0fxWpv_U3f2uDoFJEQ@mail.gmail.com> (raw)
In-Reply-To: <f59560b2-550f-4423-8428-5116fb1c6ad8@efficios.com>
[-- Attachment #1.1: Type: text/plain, Size: 1581 bytes --]
On Tue, 24 Oct 2023 at 21:56, Kienan Stewart <kstewart@efficios.com> wrote:
> Hi Lin,
>
> could you keep the lttng-dev list in CC on your replies in the future?
>
Yes, sure.
>
>
> On 2023-10-24 09:25, Lin ArcX wrote:
> > Thanks for your response. i fixed the names. here is new commands:
> > # enable event for traced functions
> > sudo lttng enable-event --kernel
> irq_handler_entry,napi_poll,net_dev_queue
> >
> > # different name with kernel
> > sudo lttng enable-event --kernel
> >
> net_if_rx_entry,net_if_rx_ni_entry,net_napi_gro_receive_entry,net_if_receive_skb_list_entry,net_if_receive_skb
> >
> > Now In new tracefile i can see a lot of new events come. but still can't
> > see any trace from these:
> >
> > net_if_rx_ni_entry
> > net_napi_gro_receive_entry
> > net_if_receive_skb_list_entry
> >
> This looks fine to me.
>
> On a linux 4.19 system, I ran a test with using lttng-modules 2.12.14. I
> saw events for "net_napi_gro_receive_entry".
>
> In parallel with the LTTng tracing session, I ran
>
> perf stat -e
>
> net:netif_rx_ni_entry,net:netif_receive_skb_list_entry,net:napi_gro_receive_entry
>
> The above allowed me to confirm that there were
> "net:napi_gro_receive_entry_events", but no "net:netif_rx_ni_entry" or
> "net:netif_receive_skb_list_entry" occurrences in my test.
>
> Are you seeing a situation where another tool is recording occurrences
> of the events that you think aren't being seen during your tracing session?
>
No, nothing, I'm running my client/server application inside wsl and no
other tools are running.
>
> thanks,
> kienan
>
[-- Attachment #1.2: Type: text/html, Size: 2423 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 prev parent reply other threads:[~2023-10-25 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 13:43 Lin ArcX via lttng-dev
2023-10-23 19:28 ` Kienan Stewart via lttng-dev
[not found] ` <CALBKf8JtZKGe5i9S0=zcU_7Qj8b_Z_FkbLv+hqcDf1BbBnZF7w@mail.gmail.com>
2023-10-24 19:59 ` Kienan Stewart via lttng-dev
[not found] ` <f59560b2-550f-4423-8428-5116fb1c6ad8@efficios.com>
2023-10-25 8:54 ` Lin ArcX via lttng-dev [this message]
2023-10-27 17:18 ` 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=CALBKf8JHM1xDf9L3m+4p-2eNQ2s6yGJw0fxWpv_U3f2uDoFJEQ@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.com \
--cc=linarcx@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