Skip to contentSkip to conversation

added colored print out of log levels

PATCH In review Eugen Wiens 2 participants 2 messages Feb 9, 2018 – Feb 13, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 added colored print out of log levels

When the system is booting the warnings and errors are not be quickly discovered. With this improvement the errors are colored red, the warnings yellow and the notices blue.

---
 common/Kconfig          |  8 ++++++++
 common/console_common.c | 29 ++++++++++++++++++++++++++++-
 2 files changed, 36 insertions(+), 1 deletion(-)
common/Kconfig +8 -0
index 57418ca..461ad35 100644
@@ -1000,6 +1000,14 @@ config DEFAULT_LOGLEVEL
 	  7    debug-level messages (debug)
 	  8    verbose debug messages (vdebug)
 
+config PRINT_COLORED_LOG_LEVEL
+	prompt "enable colored printing of the log level"
+	bool
+	default n
+	help
+		Enable the print out of the colored log level.
+
+
 config DEBUG_INFO
 	bool
 	prompt "enable debug symbols"
common/console_common.c +28 -1
index d051458..19b183f 100644
@@ -31,7 +31,21 @@
 #include <malloc.h>
 #include <asm-generic/div64.h>
 
-#ifndef CONFIG_CONSOLE_NONE
+#ifndef CONFIG_CONFIG_CONSOLE_NONE
+
+#ifdef CONFIG_PRINT_COLORED_LOG_LEVEL
+#define MAX_CHARACTERS_COLORED_LOG_LEVEL 	30
+#define MAX_LOG_LEVEL 						MSG_NOTICE
+
+static const char colored_log_level[MAX_LOG_LEVEL+2][MAX_CHARACTERS_COLORED_LOG_LEVEL] = {
+	"\033[31mEMERG:\033[0m ",		/* color red for log level MSG_EMERG */
+	"\033[31mALERT:\033[0m ",		/* color red for log level MSG_ALERT */
+	"\033[31mCRITICAL:\033[0m ",	/* color red for log level MSG_CRIT */
+	"\033[31mERROR:\033[0m ",		/* color red for log level MSG_ERR */
+	"\033[33mWARNING:\033[0m ",		/* color yellow for log level MSG_WARNING */
+	"\033[34mNOTICE:\033[0m ", 		/* color blue for log level MSG_NOTICE */
+};
+#endif
 
 int barebox_loglevel = CONFIG_DEFAULT_LOGLEVEL;
 
@@ -102,6 +116,15 @@ nolog:
 	puts(str);
 }
 
+static void print_colored_log_level(const int level)
+{
+#ifdef CONFIG_PRINT_COLORED_LOG_LEVEL
+	if (level <= MAX_LOG_LEVEL) {
+		pr_puts(level, colored_log_level[level]);
+	}
+#endif
+}
+
 int pr_print(int level, const char *fmt, ...)
 {
 	va_list args;
@@ -111,6 +134,8 @@ int pr_print(int level, const char *fmt, ...)
 	if (!IS_ENABLED(CONFIG_LOGBUF) && level > barebox_loglevel)
 		return 0;
 
+	print_colored_log_level(level);
+
 	va_start(args, fmt);
 	i = vsprintf(printbuffer, fmt, args);
 	va_end(args);
@@ -129,6 +154,8 @@ int dev_printf(int level, const struct device_d *dev, const char *format, ...)
 	if (!IS_ENABLED(CONFIG_LOGBUF) && level > barebox_loglevel)
 		return 0;
 
+	print_colored_log_level(level);
+
 	if (dev->driver && dev->driver->name)
 		ret += sprintf(printbuffer, "%s ", dev->driver->name);
 
Signature · 11 lines
2.7.4


Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen beinhalten und ist ausschließlich für die im Verteiler genannten Personen bestimmt. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. Bitte benachrichtigen Sie uns gegebenenfalls telefonisch oder mit Antwort-Mail, falls Sie nicht der richtige Adressat dieser E-Mail sind. Bitte löschen Sie diese Nachricht und alle Anhänge dazu unverzüglich. Falls nicht ausdrücklich vermerkt, ist diese E-Mail keine rechtlich bindende Vereinbarung. 

Kommanditgesellschaft: JUMO GmbH & Co. KG, Sitz: 36039 Fulda, Amtsgericht Fulda HRA 302, Persönlich haftende Gesellschafterin: M. K. JUCHHEIM GmbH, Sitz: 36039 Fulda, Amtsgericht Fulda HRB 17, Geschäftsführer: Dipl.-Ing. Bernhard Juchheim, Dipl.-Kfm. Michael Juchheim 
Ust.-Id.-Nr.: DE 112411234 
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
#1 lore raw

HI Eugen,

Quoted 2 lines · Eugen Wiens

When the system is booting the warnings and errors are not be quickly discovered. With this improvement the errors are colored red, the warnings yellow and the notices blue.

I like this because I like colors ;)
However, some people do not. Can we make this honour the value of the global.allow_color variable? This variable is currently only used in the environment, so we would have to move it to C code by adding a globalvar_add_simple_bool().

Quoted 12 lines
---
 common/Kconfig          |  8 ++++++++
 common/console_common.c | 29 ++++++++++++++++++++++++++++-
 2 files changed, 36 insertions(+), 1 deletion(-)
common/Kconfig +0 -0
index 57418ca..461ad35 100644

common/Kconfig config DEFAULT_LOGLEVEL · line 1008

Quoted 9 lines
common/Kconfig +6 -0
@@ -1000,6 +1000,14 @@ config DEFAULT_LOGLEVEL
 	  7    debug-level messages (debug)
 	  8    verbose debug messages (vdebug)
 
+config PRINT_COLORED_LOG_LEVEL
+	prompt "enable colored printing of the log level"
+	bool
+	default n
+	help
+		Enable the print out of the colored log level.

I don't think it's worth having an extra config option for this. If we get concerned about the code size, then we should rather add a global color control Kconfig option and let everything color related depend on this.

Something like:

config CONSOLE_ALLOW_COLOR
prompt "Allow colored console output"
bool

static unsigned int allow_color;

bool __console_allow_color(void)

{
	return allow_color;
}

Some initcall:

	globalvar_add_simple_bool("allow_color", &allow_color);

include/:

static inline bool console_allow_color(void)

{
	if (!IS_ENABLED(CONFIG_CONSOLE_ALLOW_COLOR))
		return false;
	return __console_allow_color();
}

Sascha

Signature · 9 lines
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox