From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 0/8] eal: dynamic logs Date: Wed, 12 Apr 2017 12:37:30 +0200 Message-ID: <3021295.5zDAG2DLiv@xps13> References: <20170329155323.4760-1-olivier.matz@6wind.com> <20170404164040.24132-1-olivier.matz@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Olivier Matz , dev@dpdk.org To: "De Lara Guarch, Pablo" Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 937192986 for ; Wed, 12 Apr 2017 12:37:32 +0200 (CEST) Received: by mail-wm0-f49.google.com with SMTP id t189so20705070wmt.1 for ; Wed, 12 Apr 2017 03:37:32 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2017-04-12 09:26, De Lara Guarch, Pablo: > Hi Olivier, > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Matz > > > > The objective of this patchset is to introduce a framework to > > support dynamic log types in EAL. It also provides one example of use > > (in i40e). > > > > Features: > > - log types are identified by a string > > - at registration, a uniq identifier is associated to a log type > > - each log type can have its level changed dynamically > > - extend command line parameters to set the log level of a specific > > type, or logs matching a regular expression > > - keep compat with other legacy types (eal, malloc, ring, user*, > > etc... keep their hardcoded log type value) > > > > Next step is to adapt drivers, libs and apps to use this new API. At the > > end, we can expect that all non-dataplane logs are moved to be dynamic, > > so we can enable/disable them at runtime, without recompiling. Many > > debug options can probably be removed from configuration: > > $ git grep DEBUG config/common_base | wc -l > > 89 [...] > With this patch, all logs that use logtype "USERX" (e.g. RTE_LOGTYPE_USER1) are not shown anymore. > Should these macro be removed? > > Right now, all applications using this won't show these, so I assume that all of them > should be fixed before the release is out. > Is that correct? Is it a bug in the commit http://dpdk.org/commit/c1b5fa9 ? Note this line: __rte_log_register("user1", 24);