public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hall, Jenna S" <jenna.s.hall@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Does MCA handler work correctly?
Date: Tue, 11 Jun 2002 16:05:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905665@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905664@msgid-missing>

Good observation - you are absolutely correct that the current
implementation is not SMP-safe.  The MCA handler is not functional yet -
currently, if you do get an MCA the OS handler will return to SAL with a
request to reboot the machine, and no attempt is made to recover.  (The
logging of hardware-corrected errors is functional, however.)

There is an effort in progress to code the OS recovery for selected MCAs.
This effort is part of the Atlas project:

http://atlas-64.sourceforge.net


Thanks,
Jenna

 -----Original Message-----
From: 	j-nomura@ce.jp.nec.com [mailto:j-nomura@ce.jp.nec.com] 
Sent:	Tuesday, June 11, 2002 5:01 AM
To:	linux-ia64@linuxia64.org
Subject:	[Linux-ia64] Does MCA handler work correctly?

Hello,

does MCA handler of 2.4.18 work correctly on multiple processors?

While looking into mca.c and mca_asm.S, they have single static stack
area for MCA handling, but I could not find synchronization code
between processors.

It seems that when MCA occurs on multiple processors, they may break
stacks each other.

Best regards.
--
NOMURA, Jun'ichi <j-nomura@ce.jp.nec.com, nomura@hpc.bs1.fc.nec.co.jp>
HPC Operating System Group, 1st Computers Software Division,
Computers Software Operations Unit, NEC Solutions.

_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64


      reply	other threads:[~2002-06-11 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 12:01 [Linux-ia64] Does MCA handler work correctly? j-nomura
2002-06-11 16:05 ` Hall, Jenna S [this message]

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=marc-linux-ia64-105590701905665@msgid-missing \
    --to=jenna.s.hall@intel.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