From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Remove limit on MCA recoveries
Date: Mon, 17 Jan 2005 21:18:47 +0000 [thread overview]
Message-ID: <7557.1105996727@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <200501152249.j0FMn6JH2857539@clink.americas.sgi.com>
On Mon, 17 Jan 2005 15:07:21 -0600 (CST),
Russ Anderson <rja@sgi.com> wrote:
>Hidetoshi Seto wrote:
>My only real complaint about the array is that the current size
>is too small. The Altix error injection test (which can modify
>the ECC to create true memory uncorrectables) can recover from
>several hundred memory uncorrectable errors, when the array
>limitation is removed. Making the array dynamic (linked list or
>something), so the size can be expanded would be a sufficient
>solution, too.
Do not even think about making the array a dynamic size. MCA events
can occur even when interrupts are disabled, which means that in an MCA
you have no idea if any of the kernel structures are in a safe state or
not. That in turn means that you cannot extend the array from MCA
context. Page flags that indicate bad memory are the best way to go.
next prev parent reply other threads:[~2005-01-17 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 22:49 [patch] Remove limit on MCA recoveries Russ Anderson
2005-01-15 23:10 ` Keith Owens
2005-01-16 9:01 ` Matthias Fouquet-Lapar
2005-01-17 1:07 ` Hidetoshi Seto
2005-01-17 19:27 ` Russ Anderson
2005-01-17 21:07 ` Russ Anderson
2005-01-17 21:18 ` Keith Owens [this message]
2005-01-17 21:28 ` Luck, Tony
2005-01-17 21:28 ` Russ Anderson
2005-01-17 22:01 ` Russ Anderson
2005-01-18 13:57 ` 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=7557.1105996727@kao2.melbourne.sgi.com \
--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