[dpdk-dev] [PATCH v3 0/8] eal: dynamic logs

Thomas Monjalon thomas.monjalon at 6wind.com
Wed Apr 12 12:37:30 CEST 2017


2017-04-12 09:26, De Lara Guarch, Pablo:
> Hi Olivier,
> 
> From: dev [mailto:dev-bounces at 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);



More information about the dev mailing list