From: Russ Anderson <rja@sgi.com>
To: mfl@kernel.paris.sgi.com (Matthias Fouquet-Lapar)
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] Remove limit on MCA recoveries
Date: Mon, 17 Jan 2005 13:27:10 -0600 (CST) [thread overview]
Message-ID: <200501171927.j0HJRAmE3010159@clink.americas.sgi.com> (raw)
In-Reply-To: <200501160901.j0G91h8G001716@mtv-vpn-hw-mfl-1.corp.sgi.com> from "Matthias Fouquet-Lapar" at Jan 16, 2005 10:01:43 AM
Matthias Fouquet-Lapar wrote:
> Keith Owens wrote:
> > Russ Anderson <rja@sgi.com> wrote:
> > >The MCA recovery driver saves the addresses of 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.
> >
> > lkcd dumps kernel pages marked reserved, so lkcd will try to process
> > isolated pages. We will eventually need to add a new page flag to mark
> > faulty pages.
>
> Probably any other dump mechanism should be aware of bad HW pages as well,
> so we might be better off to add a flag right away. While we are at it I
> would propose to have actually two flags :
>
> - hard error (which will cause a MCA and should be skipped when taking
> a system dump)
> - soft error (page has encountered SBE, so we might want to avoid future
> allocation, but it can be dumped without causing an MCA)
Yes, there should be page->flags to indicate hard and soft memory errors,
such as PG_hard_error and PG_soft_error. The dump code could look at those
flags.
include/linux/page-flags.h has PG_error for indicating I/O errors, which
is close but not quite what we need, given the way it is used.
CCing linux-kernel since the flags are not ia64 specific.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
parent reply other threads:[~2005-01-17 19:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200501160901.j0G91h8G001716@mtv-vpn-hw-mfl-1.corp.sgi.com>]
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=200501171927.j0HJRAmE3010159@clink.americas.sgi.com \
--to=rja@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfl@kernel.paris.sgi.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;
as well as URLs for NNTP newsgroup(s).