From: Robert Whitton <rwhitton@iee.org>
To: "Borislav Petkov" <bp@amd64.org>, <rwhitton@iee.org>
Cc: "Clemens Ladisch" <clemens@ladisch.de>, <linux-kernel@vger.kernel.org>
Subject: Re: Background memory scrubbing
Date: Wed, 20 Apr 2011 16:46:22 +0100 [thread overview]
Message-ID: <18563.1303314382@jupiter.eclipse.co.uk> (raw)
> On Wed, Apr 20, 2011 at 05:19:41PM +0200, Clemens Ladisch wrote:
> > > Unfortunately in common with a large number of hardware platforms
> > > background scrubbing isn't supported in the hardware (even though ECC
> > > error correction is supported) and thus there is no BIOS option to
> > > enable it.
> >
> > 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).
>
> Or even better, if on AMD, you can build the amd64_edac module
> (CONFIG_EDAC_AMD64) and do
>
> echo > /sys/devices/system/edac/mc/mc/sdram_scrub_rate
>
> where x is the scrubbing bandwidth in bytes/sec and y is the memory
> controller on the machine, i.e. node.
>
> --
> Regards/Gruss,
> Boris.
>
Unfortunately that also isn't an option on my platform(s). There surely must be a way for a module to be able to get a mapping for each physical page of memory in the system and to be able to use that mapping to do atomic read/writes to scrub the memory.
next reply other threads:[~2011-04-20 15:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 15:46 Robert Whitton [this message]
2011-04-20 16:01 ` Background memory scrubbing Borislav Petkov
2011-04-20 16:01 ` Borislav Petkov
2011-04-25 16:53 ` Chris Friesen
2011-04-25 16:53 ` Chris Friesen
-- strict thread matches above, loose matches on Subject: below --
2011-04-20 17:05 Robert Whitton
2011-04-20 17:53 ` Rik van Riel
2011-04-24 20:47 ` Pavel Machek
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 19:23 ` Bill Gatliff
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=18563.1303314382@jupiter.eclipse.co.uk \
--to=rwhitton@iee.org \
--cc=bp@amd64.org \
--cc=clemens@ladisch.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.