From: Bill Gatliff <bgat@billgatliff.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: rwhitton@iee.org, linux-kernel@vger.kernel.org
Subject: Re: Background memory scrubbing
Date: Wed, 20 Apr 2011 14:23:36 -0500 [thread overview]
Message-ID: <BANLkTimO_9UQvCPKGKYM+AeL0dwC_8CzOw@mail.gmail.com> (raw)
In-Reply-To: <4DAEF98D.2090802@ladisch.de>
Ladisch:
On Wed, Apr 20, 2011 at 10:19 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> Which hardware platform is this? AFAICT all architectures with ECC
> (old AMD64, Family 0Fh, Family 10h) also have scrubbing support.
> If your BIOS is too dumb, just try enabling it directly (bits 0-4 of
> PCI configuration register 0x58 in function 3 of the CPU's northbridge
> device, see the BIOS and Kernel's Developer's Guide for details).
That won't help non-AMD64 platforms that want to scrub.
Is there a way to make Robert's approach work? I'm aware of a few
non-AMD64, somewhat-exotic platforms that require scrubbing the way
that Robert is proposing...
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2011-04-20 19:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:40 Robert Whitton
2011-04-20 15:19 ` Clemens Ladisch
2011-04-20 15:35 ` Borislav Petkov
2011-04-20 15:46 ` Markus Trippelsdorf
2011-04-20 15:58 ` Borislav Petkov
2011-04-20 16:45 ` Markus Trippelsdorf
2011-04-20 16:55 ` Markus Trippelsdorf
2011-04-20 17:36 ` Borislav Petkov
2011-04-20 18:28 ` [PATCH] edac: Remove debugging output in scrub rate handling Markus Trippelsdorf
2011-04-21 11:55 ` Borislav Petkov
2011-04-20 19:23 ` Bill Gatliff [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-20 17:05 Background memory scrubbing Robert Whitton
2011-04-20 17:53 ` Rik van Riel
2011-04-24 20:47 ` Pavel Machek
2011-04-20 15:46 Robert Whitton
2011-04-20 16:01 ` Borislav Petkov
2011-04-25 16:53 ` Chris Friesen
2011-04-20 7:58 Robert Whitton
2011-04-20 13:30 ` Clemens Ladisch
2011-04-20 16:45 ` Rik van Riel
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=BANLkTimO_9UQvCPKGKYM+AeL0dwC_8CzOw@mail.gmail.com \
--to=bgat@billgatliff.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhitton@iee.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
all inboxes | Powered by JetHome®