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 C5040A00C4; Wed, 12 Oct 2022 14:31:33 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7873E43054; Wed, 12 Oct 2022 14:31:33 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 14B3C42EF7 for ; Wed, 12 Oct 2022 14:31:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665577891; 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=IaxSQnHY1LL1QV0pzw8MD0ynGhTwlt3cJG9U9+A27Gw=; b=InObWwkWJ15MO5rp1xyaxS5sOdID6094xYLnpbDQUpDmw/ShhyrK9lXEOlUT8nRDk57Z06 42hno1ODbTrHROIW1/hVfHVrakKV8y+2AHGJT6wHJM+76jAMGKDzhBzMwRl5pmpmdz5XRw udu97Y5QZbj02PPpIRmIkSV7MsdLz5o= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-258-eIHvKBnFP1Oat9oCkZzxvQ-1; Wed, 12 Oct 2022 08:31:28 -0400 X-MC-Unique: eIHvKBnFP1Oat9oCkZzxvQ-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4D9A7800B23; Wed, 12 Oct 2022 12:31:28 +0000 (UTC) Received: from localhost.localdomain (ovpn-193-115.brq.redhat.com [10.40.193.115]) by smtp.corp.redhat.com (Postfix) with ESMTP id 826BF1111C60; Wed, 12 Oct 2022 12:31:27 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: jerinj@marvell.com, skori@marvell.com Subject: [PATCH v3 0/9] Trace subsystem fixes Date: Wed, 12 Oct 2022 14:31:03 +0200 Message-Id: <20221012123112.2951802-1-david.marchand@redhat.com> In-Reply-To: <20220921120359.2201131-1-david.marchand@redhat.com> References: <20220921120359.2201131-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello, This series addresses a number of issues and limitations I have identified over time in the trace subsystem. The main issue was with dynamically enabling trace points which was not working if no trace point had been enabled at rte_eal_init() time. This is 22.11 material. We may start thinking about marking this API stable, but this is another topic. -- David Marchand Changes since v2: - fixed trace point name storage, Changes since v1: - split patch 3, - addressed comments on (previously) patch 4, David Marchand (9): trace: fix mode for new trace point trace: fix mode change trace: fix leak with regexp trace: rework loop on trace points trace: fix dynamically enabling trace points trace: fix race in debug dump trace: fix metadata dump trace: remove limitation on trace point name trace: remove limitation on directory app/test/test_trace.c | 67 +++++++------ app/test/test_trace.h | 2 + doc/guides/prog_guide/trace_lib.rst | 14 ++- lib/eal/common/eal_common_trace.c | 111 ++++++++++----------- lib/eal/common/eal_common_trace_ctf.c | 3 - lib/eal/common/eal_common_trace_utils.c | 81 +++++++-------- lib/eal/common/eal_trace.h | 11 +- lib/eal/include/rte_trace_point_register.h | 3 +- 8 files changed, 138 insertions(+), 154 deletions(-) -- 2.37.3