From: Alan Cox <alan@linux.intel.com>
To: Feng Tang <feng.tang@intel.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, akpm@linux-foundation.org
Subject: Re: [PATCH] console: prevent registered consoles from dumping old kernel message over again
Date: Wed, 12 Jan 2011 11:14:01 +0000 [thread overview]
Message-ID: <20110112111401.4879d928@bob.linux.org.uk> (raw)
In-Reply-To: <1294814926-1460-1-git-send-email-feng.tang@intel.com>
On Wed, 12 Jan 2011 14:48:46 +0800
Feng Tang <feng.tang@intel.com> wrote:
> For a platform with many consoles like:
> "console=tty1 console=ttyMFD2 console=ttyS0 earlyprintk=mrst"
>
> Each time when the non "selected_console" (tty1 and ttyMFD2 here) get
> registered, the existing kernel message will be printed out on
> registered consoles again, the "mrst" early console will get some
> same message for 3 times, and "tty1" will get some for twice.
>
> So try to temporarily disable registered console's printing when dump
> the existing kernel messages to the new console.
I don't think the existing behaviour should be changed because other
systems and users rely on it. Perhaps we need to be able to do
console=xxx addconsole=yyy
or some such instead so the user can indicate if the console should get
all the messages so far or just be added as an extra console
next prev parent reply other threads:[~2011-01-12 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 6:48 [PATCH] console: prevent registered consoles from dumping old kernel message over again Feng Tang
2011-01-12 11:14 ` Alan Cox [this message]
2011-01-12 14:51 ` Feng Tang
2011-01-12 14:50 ` Alan Cox
2011-01-20 0:11 ` Andrew Morton
2011-01-20 1:44 ` Feng Tang
2011-01-20 1:51 ` Andrew Morton
2011-01-20 2:31 ` Feng Tang
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=20110112111401.4879d928@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.