public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Robin Holt <holt@sgi.com>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vivek Goyal <vgoyal@redhat.com>, Haren Myneni <hbabu@us.ibm.com>,
	kexec@lists.infradead.org
Subject: Re: [PATCH 1/7] ia64, kdump: Mask MCA/INIT on freezing cpus
Date: Tue, 23 Jun 2009 00:55:36 -0500	[thread overview]
Message-ID: <20090623055536.GE6865@sgi.com> (raw)
In-Reply-To: <4A4022EA.1020506@jp.fujitsu.com>

On Tue, Jun 23, 2009 at 09:33:46AM +0900, Hidetoshi Seto wrote:
> Robin Holt wrote:
...
> Do you mean that the 2nd kernel should be able to handle MCA/INIT from its
> boot up?  I guess the word PROM is nearly equal to PAL/SAL firmware, if so
> then I don't think there are good generic interface/procedure could be
> useful here.  Do you have any concrete idea?

No concrete ideas.  Just a really uneasy feeling whenever the INIT
is disabled.

On SGI's ia64 servers, when the INIT is first received, our PROM (PAL/SAL)
records the processors state.  This record remains for the next reset
or for salinfo to transfer to disk.  We can dump all the records in a
format somewhat similar to the output in /var/log/salinfo/decoded.

On more occasions than I could even begin to describe, those records
have helped us determine what the processor was doing despite it even
ignoring interrupts.  This includes everything except when MCA/INIT
handling is disabled or PMIs are being processed.

If you could give this some consideration, I would appreciate it.
I really don't have the time to dedicate to thinking all the way through
and therefore will not stand in the way of any patch you propose.
If I can be of help in any way, please let me know.

Thanks,
Robin

  reply	other threads:[~2009-06-23  5:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  6:44 [PATCH 0/7] Patches for kdump vs. INIT Hidetoshi Seto
2009-06-18  6:46 ` [PATCH 1/7] ia64, kdump: Mask MCA/INIT on freezing cpus Hidetoshi Seto
2009-06-22 13:45   ` Robin Holt
2009-06-23  0:33     ` Hidetoshi Seto
2009-06-23  5:55       ` Robin Holt [this message]
2009-06-23  8:07         ` Hidetoshi Seto
2009-06-24 11:14           ` Robin Holt
2009-06-25  2:15             ` Hidetoshi Seto
2009-06-25  3:29               ` Robin Holt
2009-06-18  6:48 ` [PATCH 2/7] ia64, kexec: Make INIT safe while kdump/kexec Hidetoshi Seto
2009-06-18  6:48 ` [PATCH 3/7] ia64, kexec: Unregister MCA handler before kexec Hidetoshi Seto
2009-06-18  6:49 ` [PATCH 4/7] ia64, kdump: Don't offline APs Hidetoshi Seto
2009-06-18  6:50 ` [PATCH 5/7] ia64, kdump: Mask INIT first in panic-kdump path Hidetoshi Seto
2009-06-18  6:51 ` [PATCH 6/7] ia64, kdump: Try INIT regardless of kdump_on_init Hidetoshi Seto
2009-06-18  6:53 ` [PATCH 7/7] ia64, kdump: Short path to freeze CPUs Hidetoshi Seto
2009-06-22  6:31 ` [PATCH 0/7] Patches for kdump vs. INIT Jay Lan
2009-06-22  7:16   ` Hidetoshi Seto
2009-07-09  7:02 ` [PATCH v2 " Hidetoshi Seto
2009-07-09  7:10   ` [PATCH v2 1/7] ia64, kdump: Mask MCA/INIT on frozen cpus Hidetoshi Seto
2009-07-09  7:11   ` [PATCH v2 2/7] ia64, kexec: Make INIT safe while transition to kdump/kexec kernel Hidetoshi Seto
2009-07-09  7:12   ` [PATCH v2 3/7] ia64, kexec: Unregister MCA handler before kexec Hidetoshi Seto
2009-07-09  7:14   ` [PATCH v2 4/7] ia64, kdump: Don't return APs to SAL from kdump Hidetoshi Seto
2009-07-09  7:15   ` [PATCH v2 5/7] ia64, kdump: Mask INIT first in panic-kdump path Hidetoshi Seto
2009-07-09  7:17   ` [PATCH v2 6/7] ia64, kdump: Try INIT regardless of kdump_on_init Hidetoshi Seto
2009-07-09  7:18   ` [PATCH v2 7/7] ia64, kdump: Short path to freeze CPUs Hidetoshi Seto

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=20090623055536.GE6865@sgi.com \
    --to=holt@sgi.com \
    --cc=hbabu@us.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=vgoyal@redhat.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