From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64: reset console_loglevel so INIT output always goes to console
Date: Sat, 08 Jan 2005 01:32:26 +0000 [thread overview]
Message-ID: <4704.1105147946@ocs3.ocs.com.au> (raw)
In-Reply-To: <1105140871.25267.50.camel@eeyore>
On Fri, 07 Jan 2005 16:34:31 -0700,
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>Reset console_loglevel early in INIT handler. Otherwise, if
>it has been turned down (i.e., with "dmesg -n1"), the user may
>see no effect at all from issuing an INIT. We're never going
>to run any more user code, so there won't be any opportunity for
>anything to collect the output from the dmesg buffer.
That is fine for the current code base. It will have to be revisited
when we get per cpu INIT stacks and the slave INIT handler actually
does something.
We are slowly but steadily moving to recovery from some MCA events. If
one of the cpus is spinning disabled when an MCA occurs then the
disabled cpu will get a slave INIT event as part of the MCA rendezvous.
If the MCA is recoverable then the slave INIT event will also be
recoverable and will eventually return to user space.
That change is still some way off, but bear it in mind when changing
the existing code.
next prev parent reply other threads:[~2005-01-08 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 23:34 [PATCH] ia64: reset console_loglevel so INIT output always goes to Bjorn Helgaas
2005-01-08 1:32 ` Keith Owens [this message]
2005-01-09 16:24 ` Russ Anderson
2005-01-09 17:06 ` [PATCH] ia64: reset console_loglevel so INIT output always goes to console Russ Anderson
2005-01-09 23:26 ` Keith Owens
2005-01-10 4:27 ` [PATCH] ia64: reset console_loglevel so INIT output always Bjorn Helgaas
2005-01-10 7:54 ` [PATCH] ia64: reset console_loglevel so INIT output always goes to console Matthias Fouquet-Lapar
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=4704.1105147946@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox