public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] printing support for MCA/INIT
Date: Thu, 08 Jun 2006 06:29:00 +0000	[thread overview]
Message-ID: <4487C3AC.2020803@jp.fujitsu.com> (raw)
In-Reply-To: <4486BE32.80100@jp.fujitsu.com>

Luck, Tony wrote:
>> I guess there are only 2 cases actually needs to display its progress,
>> long time wait on rendezvous and INIT-monarch. 
> 
> In the MCA case, something bad has already happened to the system,
> it is possible that we will not complete printing all of the
> messages, but if they are streaming directly to the console, then
> at least we will see the first part of the messages.  If you buffer
> them to be printed later, there may be no "later", and all the
> information will be lost.
> 
> -Tony
> 

Please look my patch.

@@ -1067,6 +1170,9 @@ ia64_mca_handler(struct pt_regs *regs, s
          rh->severity = sal_log_severity_corrected;
          ia64_sal_clear_state_info(SAL_INFO_TYPE_MCA);
          sos->os_status = IA64_MCA_CORRECTED;
+    } else {
+        /* Dump buffered message to console */
+        ia64_mlogbuf_break();
      }
      if (notify_die(DIE_MCA_MONARCH_LEAVE, "MCA", regs, (long)&nd, 0, recover)
              = NOTIFY_STOP)

If MCA handler cannot recovery the error, then try to printk
all buffered messages before returning to SAL.

Isn't it enough?

H.Seto


  parent reply	other threads:[~2006-06-08  6:29 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
2006-06-08  3:39 ` Hidetoshi Seto
2006-06-08  6:01 ` Luck, Tony
2006-06-08  6:29 ` Hidetoshi Seto [this message]
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=4487C3AC.2020803@jp.fujitsu.com \
    --to=seto.hidetoshi@jp.fujitsu.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