From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Remove limit on MCA recoveries
Date: Mon, 17 Jan 2005 01:07:46 +0000 [thread overview]
Message-ID: <41EB0FE2.6050901@jp.fujitsu.com> (raw)
In-Reply-To: <200501152249.j0FMn6JH2857539@clink.americas.sgi.com>
Russ Anderson wrote:
> The MCA recovery driver saves addresses memory errors
> in an array. The array has 32 entries. The effect is
> that after 32 recoveries, the driver stops recovering.
>
> This patch removes the page_isolate array. Since the array
> was only used to see if the page is already marked reserved,
> check the reserved bit instead of the array.
This array is temporary designed for future use.
Similar to what Keith said, the array would be helpful if
something like dump application have no idea to avoid reading
MCA pages.
Roughly say, traditionally there are 2 type of pages:
1 - not reserved
2 - reserved
IMHO, there should be additional 3 type:
3 - MCA reserved, not classified, don't read
4 - Hard error (e.g. page on broken DIMM)
5 - Soft error (e.g. having poisoned data)
The MCA recovery driver just does isolation.
What the driver want to do is marking 3 to the MCA pages.
It would better if type 3 pages could be classified into 4 or 5,
and more better if type 5 pages could be recycled into the system.
Thanks,
H.Seto
next prev parent reply other threads:[~2005-01-17 1:07 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 [this message]
2005-01-17 19:27 ` Russ Anderson
2005-01-17 21:07 ` Russ Anderson
2005-01-17 21:18 ` Keith Owens
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=41EB0FE2.6050901@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