From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: dmesg Support
Date: Tue, 30 Sep 2014 16:22:02 +0200 [thread overview]
Message-ID: <1412086926-27167-1-git-send-email-s.hauer@pengutronix.de> (raw)
Printing informations during startup is very useful, but due to slow serial
printouts it adds to the startup time of barebox. This series adds logbuffer
support and a 'dmesg' command, so it becomes possible to reduce the loglevel
while the messages are still available later. As a bonus the timestamp for
each message is recorded so that together with CONFIG_DEBUG_INITCALLS detailed
timing information of the startup process can be collected.
The dmesg support nearly compiles away when it's disabled.
Sascha
----------------------------------------------------------------
Sascha Hauer (4):
clock: Add a variable with the first timestamp after startup
clock: make get_time_ns() safe to be called without clocksource
startup: Don't print multiple lines with pr_info
Introduce message logging support
commands/Kconfig | 7 +++
commands/Makefile | 1 +
commands/dmesg.c | 100 +++++++++++++++++++++++++++++++++++++
common/Kconfig | 3 ++
common/clock.c | 11 +++++
common/console_common.c | 129 ++++++++++++++++++++++++++++++++++++++++++++++--
common/version.c | 4 +-
drivers/base/driver.c | 22 ---------
include/clock.h | 2 +
include/printk.h | 17 +++++++
10 files changed, 270 insertions(+), 26 deletions(-)
create mode 100644 commands/dmesg.c
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-09-30 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 14:22 Sascha Hauer [this message]
2014-09-30 14:22 ` [PATCH 1/4] clock: Add a variable with the first timestamp after startup Sascha Hauer
2014-09-30 14:22 ` [PATCH 2/4] clock: make get_time_ns() safe to be called without clocksource Sascha Hauer
2014-09-30 14:22 ` [PATCH 3/4] startup: Don't print multiple lines with pr_info Sascha Hauer
2014-09-30 14:22 ` [PATCH 4/4] Introduce message logging support Sascha Hauer
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=1412086926-27167-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox