From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7BDC443214 for ; Fri, 27 Oct 2023 10:11:32 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3FB204029A; Fri, 27 Oct 2023 10:11:32 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 05EE640272 for ; Fri, 27 Oct 2023 10:11:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1698394290; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6e6k/1JT5eH+exxNk851v65KVaCCgJ4hfAZWEmgMTSw=; b=eWU8mBvzAmxIoG+b3dEgGTc3N9OnA6GHNxtxxdE33LAFR8bbYZsGQTVtlHiKJJ7ycBYYcF gPJJDIfMLDGe7b+AbiIciaTysINo5G/1xr6EIvRt8TTt0vbqusDrePZ2OkbRaAua2wiux/ VajgKSVcG1gnpEb2cEAyQ2j5LRyBtZg= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-623-mTlnq7lMOnS9p5hdYOG4zw-1; Fri, 27 Oct 2023 04:11:28 -0400 X-MC-Unique: mTlnq7lMOnS9p5hdYOG4zw-1 Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2c520e0a9a7so19764081fa.3 for ; Fri, 27 Oct 2023 01:11:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698394287; x=1698999087; h=content-transfer-encoding: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=6e6k/1JT5eH+exxNk851v65KVaCCgJ4hfAZWEmgMTSw=; b=PXoppt0AvxFzAV+rG4/62XvmSKoB+10OtIuyKcEoes5baAyKpYiUOiAYzcTYNeK/qC wLTtjWWfw7udYjhoQPtW0QajFeQPPQpleYoywzsqMjkQ9DPn7AOnYsOJ7F0o6eQxK0r1 fduE2LkemOxNkTlyHzCb6sietBPSCKrJYa8OBpF5Aj6GLcAgVs9iviNvtasxhZLR30QT NnU9kG04plBu2rc6TEjdzGCTjz0pY2Y5rUdUduQkU/abTAd4UMZ1Br9oWtDlkztP33Hz Z2UAGVbL3k03k7VEZgq9XUQ9miN6idLUGkM96G0Gq0Zl9t8hOGhpEh2fcWrEjZFR0ABF sa6A== X-Gm-Message-State: AOJu0YxirEhfUL/YPzmiA5/ruE6I2UwZS4PV3zcyNZjn40lZ4T7mZR5h EfHB7KeVYMWundx79qfRosFtHBaQiTp3hAO3DJKEDefThfbmA4H5fcedq/VKGPEFHykVQfuA8cs +lOZB/cOGXlejd9+IwDp32A== X-Received: by 2002:a2e:9881:0:b0:2c5:50d:3fc3 with SMTP id b1-20020a2e9881000000b002c5050d3fc3mr1451288ljj.7.1698394287455; Fri, 27 Oct 2023 01:11:27 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEiLA+MwzuKWmghUS7JXExjX5d5Vy1LuYbu0z0Q72mNuilS2o2rTF134wHst7T60C9fc8DWHLqv9fe88QnGORI= X-Received: by 2002:a2e:9881:0:b0:2c5:50d:3fc3 with SMTP id b1-20020a2e9881000000b002c5050d3fc3mr1451270ljj.7.1698394287103; Fri, 27 Oct 2023 01:11:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Fri, 27 Oct 2023 10:11:15 +0200 Message-ID: Subject: Re: [dpdk-users] Unable to see traces from a user defined DPDK Tracepoint To: Sanjit Kumar Cc: users@dpdk.org, "utkarshece80587@gmail.com" , "4plague@gmail.com" <4plague@gmail.com>, Jerin Jacob Kollanukkaran , Sunil Kumar Kori X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hello, Copying trace framework maintainers. On Fri, Oct 27, 2023 at 9:48=E2=80=AFAM Sanjit Kumar wrote: > I am trying to test the usage of the DPDK trace library. I have run into = the same issue as recounted here - https://mails.dpdk.org/archives/users/20= 20-December/005266.html - where I am able to build and run my DPDK applica= tion where I have created and registered my custom trace point (verified vi= a rte_trace_dump(stdout) which says my traces are 'enabled' - i see the rig= ht trace buffer size, trace file destination etc). The trace point creation= and registration are identical to what is mentioned in the program guide u= sing RTE_TRACE_POINT in a header file and registering it in my dpdk applica= tion via RTE_TRACE_POINT_REGISTER macro. > > What I notice are as follows: > > 1. The program builds and runs as intended. > 2. The trace files are generated in the correct destination directory. > 3. On using trace=3D.* ----> I see a huge list of traces on viewing the = trace file with babeltrace - but do not see my custom trace point. I also d= o not see any trace output from my dpdk application if I reuse DPDK library= traces ( eg: rte_eal_trace_thread_lcore_ready ) instead of defining my own= custom traces. > 4. On using trace=3D i do not se= e any trace output just used inside my application. > > I think the above observations suggest that the issue might be in configu= ring my DPDK application to recognize and create trace output properly. How= ever the rte_trace_dump output suggests that trace is enabled here. > > What I would like to know is similar to utkarsh's question: > Is there anything I am missing in configuring my application to recognize= traces? If so can you please point it out? I think a hint was posted later, about this topic. Did you compile your application tracepoint register code with -DALLOW_EXPERIMENTAL_API ? If you confirm it solves your issue, we need to enhance the trace framework documentation. --=20 David Marchand