From: "Fabio M. Di Nitto" <fabbione@fabbione.net>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <gregkh@suse.de>
Subject: Re: [PATCH] kernel/printk: do not turn off bootconsole in printk_late_init if keep_bootcon
Date: Mon, 15 Aug 2011 14:03:56 +0200 [thread overview]
Message-ID: <4E490B2C.5000900@fabbione.net> (raw)
In-Reply-To: <1312934553-17085-1-git-send-email-nacc@us.ibm.com>
On 8/10/2011 2:02 AM, Nishanth Aravamudan wrote:
> It seems that commit 7bf693951a8e5f7e600a45b74d91d962a453146e doesn't
> always achieve what it aims, as printk_late_init() runs it
> unconditionally turns off all boot consoles. With this patch, I am able
> to see more messages on the boot console in KVM guests than I can
> without, when keep_bootcon is specified.
>
> Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Cc: Greg KH <gregkh@suse.de>
> ---
> kernel/printk.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/printk.c b/kernel/printk.c
> index 37dff34..293a6cc 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -1602,7 +1602,7 @@ static int __init printk_late_init(void)
> struct console *con;
>
> for_each_console(con) {
> - if (con->flags & CON_BOOT) {
> + if (!keep_bootcon && con->flags & CON_BOOT) {
> printk(KERN_INFO "turn off boot console %s%d\n",
> con->name, con->index);
> unregister_console(con);
Patch looks ok to me, just send it through the right channels for inclusion.
Fabio
next prev parent reply other threads:[~2011-08-15 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 0:02 [PATCH] kernel/printk: do not turn off bootconsole in printk_late_init if keep_bootcon Nishanth Aravamudan
2011-08-15 12:03 ` Fabio M. Di Nitto [this message]
2011-08-20 0:10 ` Andrew Morton
2011-08-23 18:41 ` Nishanth Aravamudan
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=4E490B2C.5000900@fabbione.net \
--to=fabbione@fabbione.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.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