From: Alex Williamson <alex.williamson@hp.com>
To: Russ Anderson <rja@sgi.com>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, tglx@linutronix.de,
Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/2] Migrate data off physical pages with corrected memory errors (Version 7)
Date: Mon, 21 Jul 2008 13:11:39 -0600 [thread overview]
Message-ID: <1216667499.8806.79.camel@lappy> (raw)
In-Reply-To: <20080720173914.GA9409@sgi.com>
On Sun, 2008-07-20 at 12:39 -0500, Russ Anderson wrote:
> On Sat, Jul 19, 2008 at 12:37:11PM +0200, Andi Kleen wrote:
> > If you really wanted to do this you probably should hook it up
> > to mcelog's (or the IA64 equivalent) DIMM database
>
> Is there an IA64 equivalent? I've looked at the x86_64 mcelog,
> but have not found a IA64 version.
There's a bit in the SAL error record that can tell you when the
platform thinks the page should be deallocated. In the section header
(B2.2), ERROR_RECOVERY_INFO, bit 3 "Error threshold exceeded". If you
use this bit, then it's a platform decision. If you want pages to be
deallocated on the first hit, then have your SAL always set that bit. I
believe HP systems do implement this bit in SAL using some kind of
heuristics.
Alex
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2008-07-21 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 20:35 [PATCH 0/2] Migrate data off physical pages with corrected memory errors (Version 7) Russ Anderson
2008-07-19 10:37 ` Andi Kleen
2008-07-19 12:13 ` Matthew Wilcox
2008-07-19 15:06 ` Andi Kleen
2008-07-20 17:50 ` Russ Anderson
2008-07-20 17:39 ` Russ Anderson
2008-07-21 19:11 ` Alex Williamson [this message]
2008-07-21 19:45 ` Russ Anderson
2008-07-21 19:40 ` Andi Kleen
2008-07-28 21:44 ` Russ Anderson
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=1216667499.8806.79.camel@lappy \
--to=alex.williamson@hp.com \
--cc=andi@firstfloor.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rja@sgi.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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