Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Lin ArcX <linarcx@gmail.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: Fri, 27 Oct 2023 13:18:35 -0400	[thread overview]
Message-ID: <833d916a-4bed-4802-94c1-5f39853c527e@efficios.com> (raw)
In-Reply-To: <CALBKf8JHM1xDf9L3m+4p-2eNQ2s6yGJw0fxWpv_U3f2uDoFJEQ@mail.gmail.com>

Hi Lin,

On 2023-10-25 04:54, Lin ArcX wrote:
>     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.
> 

Perhaps your test program isn't causing the WSL kernel to hit the 
`net_if_rx_ni_entry`, `net_napi_gro_receive_entry`, and 
`net_if_receive_skb_list_entry tracepoints` during your tracing session?

I recommend using `perf` to double-check that there are indeed none of 
those tracepoints being hit during a tracing session.

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:18 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
2023-10-27 17:18         ` 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=833d916a-4bed-4802-94c1-5f39853c527e@efficios.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