From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: Olivier Matz <olivier.matz@6wind.com>, david.marchand@6wind.com
Subject: Re: [PATCH] log: do not drop debug logs at compile time
Date: Fri, 30 Sep 2016 11:33:16 +0200 [thread overview]
Message-ID: <2969629.OOuc7vtRSA@xps13> (raw)
In-Reply-To: <1474011832-29987-1-git-send-email-olivier.matz@6wind.com>
2016-09-16 09:43, Olivier Matz:
> Today, all logs whose level is lower than INFO are dropped at
> compile-time. This prevents from enabling debug logs at runtime using
> --log-level=8.
>
> The rationale was to remove debug logs from the data path at
> compile-time, avoiding a test at run-time.
>
> This patch changes the behavior of RTE_LOG() to avoid the compile-time
> optimization, and introduces the RTE_LOG_DP() macro that has the same
> behavior than the previous RTE_LOG(), for the rare cases where debug
> logs are in the data path.
>
> So it is now possible to enable debug logs at run-time by just
> specifying --log-level=8. Some drivers still have special compile-time
> options to enable more debug log. Maintainers may consider to
> remove/reduce them.
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
I think it is a good change.
However I'm not sure we should take it for 16.11 as it was sent late and
there is no review comment.
It is neither really a fix nor really a feature.
If there are some +1, and no opinions against, it will go in 16.11.
Note that some drivers would need some changes to fully benefit of
debug logs enabled at run-time.
next prev parent reply other threads:[~2016-09-30 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 7:43 [PATCH] log: do not drop debug logs at compile time Olivier Matz
2016-09-30 9:33 ` Thomas Monjalon [this message]
2016-09-30 15:48 ` Wiles, Keith
2016-10-03 15:02 ` Olivier Matz
2016-10-03 15:27 ` Wiles, Keith
2016-10-03 15:37 ` Olivier Matz
2016-10-03 16:27 ` Wiles, Keith
2016-10-04 8:28 ` David Marchand
2016-10-05 12:01 ` Olivier Matz
2016-10-04 8:26 ` David Marchand
2016-10-05 11:57 ` Olivier Matz
2016-11-23 15:34 ` [PATCH v2] " Olivier Matz
2016-12-05 14:08 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2969629.OOuc7vtRSA@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.