public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] printing support for MCA/INIT
Date: Wed, 07 Jun 2006 13:28:58 +0000	[thread overview]
Message-ID: <7710.1149686938@ocs3.ocs.com.au> (raw)
In-Reply-To: <4486BE32.80100@jp.fujitsu.com>

Hidetoshi Seto (on Wed, 07 Jun 2006 20:53:22 +0900) wrote:
>Printing message to console from MCA/INIT handler is useful,
>however doing oops_in_progress = 1 in them exactly makes
>something in kernel wrong.
>Especially it sounds ugly if system goes wrong after returning
>from recoverable MCA.
>
>This patch adds ia64_mca_printk() function that collects messages
>into temporary-not-so-large message buffer during in MCA/INIT
>environment and print them out later, after returning to normal
>context or when handlers determine to down the system.

NAK this patch.  The handlers print their progress as they perform the
MCA/INIT rendezvous.  That information is critical for diagnosing any
problems with entering the handlers, it must not be delayed until the
handlers have exited.

The correct fix is to make printk safe against non maskable interrupts
and to allow polled console I/O when interrupts are disabled.  That
fixes printk from NMI error handlers in all architectures, not just
ia64.


  reply	other threads:[~2006-06-07 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 11:53 [PATCH] printing support for MCA/INIT Hidetoshi Seto
2006-06-07 13:28 ` Keith Owens [this message]
2006-06-08  3:39 ` Hidetoshi Seto
2006-06-08  6:01 ` Luck, Tony
2006-06-08  6:29 ` Hidetoshi Seto
2006-06-08  6:36 ` Keith Owens
2006-06-08 10:27 ` Hidetoshi Seto
2006-09-15  2:31 ` Hidetoshi Seto
2006-09-15  3:12 ` Russ Anderson

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=7710.1149686938@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