From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 2NlJE7/XOGUzaTYAWB0awg (envelope-from ) for ; Wed, 25 Oct 2023 04:54:23 -0400 Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=lists.lttng.org header.i=@lists.lttng.org header.a=rsa-sha256 header.s=default header.b=nB90+56m; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 4B4FA1E0C1; Wed, 25 Oct 2023 04:54:23 -0400 (EDT) Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 19DB71E00F for ; Wed, 25 Oct 2023 04:54:21 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1698224060; bh=zabZ2Nc7qGSNZrxt7kxAwS0OkM0FqJhnAZcUppK6S4U=; h=References:In-Reply-To:Date:To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=nB90+56myW3/Yu3SZJ3+WRDK4bzpR92OezTVWSOcXnPaIiwP2C3n2HZgpqZsJbNH9 F//uPVF/4qd07a23SIqsSjtIkXf6EqnM6YqVSz8NpTdkZrG1j7gmnCnz/h+EgADbKN 3RTlxyNKQQIG/M4NC7fQ98XZkxrZdSxwTNfnpN6B/1m6jp9LD01v6uD4iTY2XRIO/v nW0QQjHTDHH4Wmydexj3oeBJIRQWQUSSsc87vp4wwk54G9ZwYCVywI0sX2fYWbHgR6 1eK+ki7599WO2feEF8rkr8xYJl1abjQrpzgf7CnR7jgV5HN4HCe1qvTY9toS0NnDQA ujPvTrCt7mQAQ== Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4SFjR059v7z7l7; Wed, 25 Oct 2023 04:54:20 -0400 (EDT) Received: from mail-oa1-x32.google.com (mail-oa1-x32.google.com [IPv6:2001:4860:4864:20::32]) by lists.lttng.org (Postfix) with ESMTPS id 4SFjQz28YDz8L2 for ; Wed, 25 Oct 2023 04:54:19 -0400 (EDT) Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-1dd5b98d9aeso335092fac.0 for ; Wed, 25 Oct 2023 01:54:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698224058; x=1698828858; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pw0+W+Gtu6wfaM8X0H5BlT57/h6KMJx0TkIkMeZzcVA=; b=A89MQtIuTRAObzF+hp88QCEgglnvHtGmZEpp9QUWboI7WyH9AXEpDwipJKRuxoMA0L NaqOGoJg3HTrUO4N+x37wgv1mY0mMF1CwVMSfXEyjNuxCFuECTyMllhvz3yJQBnKd+Ak TcsvBFLkpprGJMrz4R43tHOPDyqh/CkYqHOmxWQE3knAhATeBf2j0ipCY/CNDpN9YE+V smTKhjEDepvuCzJr9FE643JJ/BLwPBy9vVF8FfEF2T5C9Mia2rOTti6yWM9Zy/G9r8yn Pu0eLXTa7z1my9sx1dVyvNU91QbZf77DdGTuneL9TRA+v5lEcMPTKDUdsyn3g4CmSEvz PwQQ== X-Gm-Message-State: AOJu0YwyPz4sf1tyTNVaOCS9MWvwuHgd+jw4jOscootLCLdm8iaQkxsJ g1lMJ6F2TlrrueKa5OyMwGPD8GHSfQ/80Bn0clA= X-Google-Smtp-Source: AGHT+IE235jsTpK2olt3a7z47VU+ZDkAF43lXRks44L+nPY0wWvQVuC30qnh3l9wsfqAbbVxhLXZFsM6iNW3eDecXmo= X-Received: by 2002:a05:6870:13c6:b0:1e9:b5d7:4000 with SMTP id 6-20020a05687013c600b001e9b5d74000mr7549131oat.7.1698224058186; Wed, 25 Oct 2023 01:54:18 -0700 (PDT) MIME-Version: 1.0 References: <2eaa5b1f-c3b2-4790-bf45-dadb66f45d48@efficios.com> In-Reply-To: Date: Wed, 25 Oct 2023 10:54:07 +0200 Message-ID: To: Kienan Stewart Cc: lttng-dev@lists.lttng.org Subject: Re: [lttng-dev] Can't receive a lot of functions that i registerd as trace-points X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Lin ArcX via lttng-dev Reply-To: Lin ArcX Content-Type: multipart/mixed; boundary="===============2274719005726193942==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============2274719005726193942== Content-Type: multipart/alternative; boundary="000000000000bcd76b0608869934" --000000000000bcd76b0608869934 Content-Type: text/plain; charset="UTF-8" On Tue, 24 Oct 2023 at 21:56, Kienan Stewart 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 > --000000000000bcd76b0608869934 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, 24 Oct 2023 at 21:56, Kienan = Stewart <kstewart@efficios.com<= /a>> wrote:
H= i Lin,

could you keep the lttng-dev list in CC on your replies in the future?
<= /blockquote>
Yes, sure.=C2=A0


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_q= ueue
>
> # 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_r= eceive_skb_list_entry,net_if_receive_skb
>
> Now In new tracefile=C2=A0i can see a lot of new events come. but stil= l 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

=C2=A0 =C2=A0perf 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 sess= ion?

No, nothing, I'm running my cl= ient/server application inside wsl and no other tools are running.=C2=A0=C2= =A0

thanks,
kienan
--000000000000bcd76b0608869934-- --===============2274719005726193942== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============2274719005726193942==--