[lkml]   [2008]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0 of 3] Low memory corruption detection and workaround
On Monday 08 September 2008 01:24, Alan Jenkins wrote:
> Jeremy Fitzhardinge wrote:
> > Hi Ingo,
> >
> > This series implements a check and workaround for memory corruption in
> > low memory.
> >
> > The first patch adds the basic mechanism. The second adds some
> > enchancements from Hugh, namely periodic scanning for badness. The
> > third tidies the user interface up by adding a proper Kconfig option
> > and several kernel command-line parameters to enable the feature and
> > control the amount of memory it scans and how often. It also uses a
> > WARN() with the intention of getting any output into
> >
> > I've tested it as far as I can, but none of my systems seem to exhibit
> > this type of corruption so I haven't seen the failure case output. I
> > hope Alan and Rafał can test this version of the patch and report it
> > does the expected thing.
> >
> > [ Hugh - I took the liberty of splitting your patch up into a delta on
> > top of mine, moving the pure bugfixes into my base patch, and
> > putting your additional code into the new patch From you with your
> > sign-off from the original patch, and adding my own sob to reflect
> > the changes I made. I hope you don't mind. ]

Why not high memory as well? We put page tables there too...

(rant: why can we still buy non-ECC memory?)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2008-09-08 13:25    [W:0.070 / U:1.016 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site