From: Anton Vorontsov <anton.vorontsov@linaro.org>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, ccross@android.com,
gregkh@linuxfoundation.org, keescook@chromium.org,
tony.luck@intel.com, arnd@arndb.de, john.stultz@linaro.org,
shuahkhan@gmail.com, arve@android.com, rebecca@android.com,
jj@chaosbits.net, rdunlap@xenotime.net, sboyd@codeaurora.org,
thomas@m3y3r.de, akpm@linux-foundation.org,
marco.stornelli@gmail.com, xiyou.wangcong@gmail.com,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
linaro-kernel@lists.linaro.org, patches@linaro.org,
kernel-team@android.com, mingo@elte.hu, a.p.zijlstra@chello.nl,
rusty@rustcorp.com.au
Subject: Re: [PATCH/RFC] Make sure linux_banner is the first message in log_buf
Date: Tue, 22 May 2012 20:59:50 -0700 [thread overview]
Message-ID: <20120523035949.GA4966@lizard> (raw)
In-Reply-To: <20120522.225512.1427265315315004011.davem@davemloft.net>
On Tue, May 22, 2012 at 10:55:12PM -0400, David Miller wrote:
> From: Anton Vorontsov <anton.vorontsov@linaro.org>
> Date: Tue, 22 May 2012 19:35:16 -0700
>
> > For scripting it is important to have a consistent header that tells
> > where the kernel log starts. At least to me it always seemed that
> > linux_banner served this purpose.
>
> Your change will not achieve this goal, many architectures
> print things long before control passes to init/main.c
If they use printk, we'll catch these messages, no? It is true that
if they just write to the HW directly, the messages are lost for us,
and there's nothing we can do about it (and we don't see these
messages from the kernel anyway, neither in dmesg, nor in pstore).
So, for serial (or arch-specific) console it is still cumbersome to
make proper parsing of all messages, but for pstore/ramconsole it is
OK. So, I dunno. I guess I'll have to add a custom header to pstore,
heh.
Thanks,
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2012-05-23 4:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:17 [PATCH v4 0/16] Merge ram_console into pstore, and more Anton Vorontsov
2012-05-22 14:17 ` [PATCH 01/16] pstore/inode: Make pstore_fill_super() static Anton Vorontsov
2012-05-22 15:24 ` Kees Cook
2012-05-22 14:17 ` [PATCH 02/16] pstore/ram: Should update old dmesg buffer before reading Anton Vorontsov
2012-05-22 15:25 ` Kees Cook
2012-05-22 14:17 ` [PATCH 03/16] pstore/ram_core: Do not reset restored zone's position and size Anton Vorontsov
2012-05-22 18:06 ` Colin Cross
2012-05-23 2:35 ` [PATCH/RFC] Make sure linux_banner is the first message in log_buf Anton Vorontsov
2012-05-23 2:50 ` Linus Torvalds
2012-05-23 2:55 ` David Miller
2012-05-23 3:59 ` Anton Vorontsov [this message]
2012-05-22 14:17 ` [PATCH 04/16] pstore/ram_core: Factor persistent_ram_zap() out of post_init() Anton Vorontsov
2012-05-22 15:26 ` Kees Cook
2012-05-22 14:17 ` [PATCH 05/16] pstore/ram: Should zap persistent zone on unlink Anton Vorontsov
2012-05-22 15:27 ` Kees Cook
2012-05-22 14:17 ` [PATCH 06/16] pstore: Add console log messages support Anton Vorontsov
2012-05-22 14:17 ` [PATCH 07/16] pstore/ram: Introduce ramoops_context.max_dump_count Anton Vorontsov
2012-05-22 15:27 ` Kees Cook
2012-05-22 14:17 ` [PATCH 08/16] pstore/ram: Factor dmesg przs initialization out of probe() Anton Vorontsov
2012-05-22 15:29 ` Kees Cook
2012-05-22 14:17 ` [PATCH 09/16] pstore/ram: Factor ramoops_get_dump_prz() out of ramoops_pstore_read() Anton Vorontsov
2012-05-22 15:32 ` Kees Cook
2012-05-22 14:17 ` [PATCH 10/16] pstore/ram: Add console messages handling Anton Vorontsov
2012-05-22 15:37 ` Kees Cook
2012-05-22 14:17 ` [PATCH 11/16] pstore/ram_core: Silence some printks Anton Vorontsov
2012-05-22 14:17 ` [PATCH 12/16] pstore/ram: Add some more documentation and examples Anton Vorontsov
2012-05-22 14:17 ` [PATCH 13/16] staging/android: Remove ram_console driver Anton Vorontsov
2012-05-22 14:17 ` [PATCH 14/16] pstore/ram_core: Remove now unused code Anton Vorontsov
2012-05-22 14:17 ` [PATCH 15/16] pstore/platform: Make automatic updates interval configurable Anton Vorontsov
2012-05-22 15:39 ` Kees Cook
2012-05-22 14:17 ` [PATCH 16/16] pstore/platform: Disable automatic updates by default Anton Vorontsov
2012-05-22 15:42 ` Kees Cook
2012-05-22 18:19 ` [PATCH v4 0/16] Merge ram_console into pstore, and more Greg Kroah-Hartman
2012-05-22 18:33 ` Kees Cook
2012-05-22 19:04 ` Greg Kroah-Hartman
2012-05-22 19:09 ` Kees Cook
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=20120523035949.GA4966@lizard \
--to=anton.vorontsov@linaro.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=ccross@android.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jj@chaosbits.net \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=mingo@elte.hu \
--cc=patches@linaro.org \
--cc=rdunlap@xenotime.net \
--cc=rebecca@android.com \
--cc=rusty@rustcorp.com.au \
--cc=sboyd@codeaurora.org \
--cc=shuahkhan@gmail.com \
--cc=thomas@m3y3r.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox