09/04/2021 13:04, David Marchand: > Add a log message when registering log types and changing log levels. > > __rte_log_register previous handled both legacy and dynamic logtypes. > To simplify the code, __rte_log_register is reworked to only handle > dynamic logtypes and takes a log level. > > Example: > $ DPDK_TEST=logs_autotest ./build/app/test/dpdk-test --no-huge -m 512 \ > --log-level=lib.eal:debug > ... > RTE>>logs_autotest > == dynamic log types > EAL: logtype1 logtype level changed from disabled to info > EAL: logtype2 logtype level changed from disabled to info > EAL: logtype1 logtype level changed from info to error > EAL: logtype3 logtype level changed from error to emerg > EAL: logtype2 logtype level changed from info to emerg > EAL: logtype3 logtype level changed from emerg to debug > EAL: logtype1 logtype level changed from error to debug > EAL: logtype2 logtype level changed from emerg to debug
This needs to be updated: logtype -> log > error message > critical message > critical message > error message > == static log types > TESTAPP1: error message > TESTAPP1: critical message > TESTAPP2: critical message > TESTAPP1: error message > Test OK > > Suggested-by: Ilya Maximets <i.maxim...@ovn.org> > Signed-off-by: David Marchand <david.march...@redhat.com> > Acked-by: Andrew Rybchenko <arybche...@solarflare.com> > Acked-by: Lukasz Wojciechowski <l.wojciec...@partner.samsung.com> Acked-by: Thomas Monjalon <tho...@monjalon.net>