From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH] printk: add boot_quiet param to support deferred printk while booting
Date: Fri, 23 Nov 2012 05:07:29 +0200 [thread overview]
Message-ID: <20121123030729.GB4030@tarshish> (raw)
In-Reply-To: <1353639022-13273-1-git-send-email-Barry.Song@csr.com>
Hi Barry,
On Fri, Nov 23, 2012 at 10:50:22AM +0800, Barry Song wrote:
[...]
> diff --git a/kernel/printk.c b/kernel/printk.c
> index 2d607f4..0b88d6bf 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -250,6 +250,9 @@ static u32 clear_idx;
> #define LOG_ALIGN __alignof__(struct log)
> #endif
> #define __LOG_BUF_LEN (1 << CONFIG_LOG_BUF_SHIFT)
> +static char __boot_log_buf[__LOG_BUF_LEN] __aligned(LOG_ALIGN);
Since we do not use this buffer when the system is running, is there a way to
release it once its content has been written to console?
baruch
> +static int boot_log_len;
> +
> static char __log_buf[__LOG_BUF_LEN] __aligned(LOG_ALIGN);
> static char *log_buf = __log_buf;
> static u32 log_buf_len = __LOG_BUF_LEN;
> @@ -1247,6 +1250,16 @@ module_param(ignore_loglevel, bool, S_IRUGO | S_IWUSR);
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-11-23 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 2:50 [RFC][PATCH] printk: add boot_quiet param to support deferred printk while booting Barry Song
2012-11-23 3:07 ` Baruch Siach [this message]
2012-11-23 3:24 ` Barry Song
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=20121123030729.GB4030@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@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