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 347E1A0543; Tue, 4 Oct 2022 11:44:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CB1D840DFB; Tue, 4 Oct 2022 11:44:39 +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 76CB340DDC for ; Tue, 4 Oct 2022 11:44:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664876676; 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=Z9Dg840KYO2c+nQckbn4B3ZVoCNYgWaLGL0BorZ2H90=; b=OMAwRz6klpN5E+j1UL3NYCMo3fqulwED6KJ75QauLnD3oXsywlTCGQJ+zODDWWDgsJCT3S h5bRg84i5Carvt89zfJIg4qVTpYq0Q6k4HJGZsva4TQYDmf3PL/bQ67q+xq+IGK+VyReQ/ 3HVCK5Y6YraKwSDJvC2b+8phvJOLMHs= 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-662-GIYAo9_zONC0WV7mTfC61A-1; Tue, 04 Oct 2022 05:44:35 -0400 X-MC-Unique: GIYAo9_zONC0WV7mTfC61A-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 65187101A528; Tue, 4 Oct 2022 09:44:35 +0000 (UTC) Received: from localhost.localdomain (unknown [10.40.195.42]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6E036492CA2; Tue, 4 Oct 2022 09:44:34 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: skori@mavell.com, jerinj@marvell.com Subject: [PATCH v2 0/9] Trace subsystem fixes Date: Tue, 4 Oct 2022 11:44:09 +0200 Message-Id: <20221004094418.196544-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.9 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 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 +-- 7 files changed, 136 insertions(+), 153 deletions(-) -- 2.37.3