Committed revision 2180.

Fabio

On Tue, 2009-05-12 at 13:37 +0200, Fabio M. Di Nitto wrote:
> Hi,
> 
> this is an unfortunate intrusive patch, but I don't see an easier way
> out without adding a lot of hacks around. IMHO better do it clean now
> than having to carry a lot of dirt around.
> 
> It changes the internal API and the amount of data are stored from the
> flight recorder (to add tag tracking).
> 
> the patch does:
> - clearly divide tags from priority. Before this was an incredible mix
> that lead to tons of little hacks around when handling priority (see a
> bunch of level+1 level-1).
> - clearly define what TAG_LOG means.
> - rewrite ENTER and LEAVE macro to use _logsys_log_printf rather than
> _logsys_log_rec and have consistent behavior across tracing messages.
> - set priority to LOGSYS_LEVEL_DEBUG to all tracing messages.
> - add tag filter check to print to logs.
> - don't automatically init subsystem tags to LOGSYS_TAG_LOG since
> expected behaviour says that everything that goes via log_printf should
> go to all logs (and hence set TAG_LOG).
> - update flight recorder to handle tag and remove duplicate code.
> - cleanup a couple of white spaces here and there.
> - fix tracing messages that were sent with
> LOGSYS_LEVEL_OMGTHEWORLDISFALLINGAPART priority everywhere
> - allow OR`ed tags as it is supposed to be and not exclusive (in
> configuration)
> 
> Fabio
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais

_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to