linux-kernel - Re: [PATCH] x86_64: early memtest to find bad ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440803212348i637d49d5r3393b6d9d2ecb0f4@mail.gmail.com>
Date:	Fri, 21 Mar 2008 23:48:01 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Willy Tarreau" <w@....eu>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86_64: early memtest to find bad ram

On Fri, Mar 21, 2008 at 10:45 PM, Willy Tarreau <w@....eu> wrote:
>
> On Fri, Mar 21, 2008 at 03:29:19PM +0100, Ingo Molnar wrote:
>  >
>  > * H. Peter Anvin <hpa@...or.com> wrote:
>  >
>  > >> very nice patch! I always thought that this was the proper way to do
>  > >> memtest - and we could in fact also do something like this after SMP
>  > >> bringup, and hit the memory bus via multiple CPUs. [that will need a
>  > >> different enumeration though than e820 maps]
>  > >>
>  > >> one structural observation: please make this unified functionality,
>  > >> so that 32-bit kernels can make use of it too.
>  > >>
>  > >
>  > > Indeed.  Of course, it would also be nice if distros shipped
>  > > bootloader-invoked prekernel test software, like memtest86+, by
>  > > default.
>  >
>  > some do (Fedora for example), but it's still a bit quirky for users to
>  > invoke and it would be nice to see those results in the kernel log as
>  > well and flag possibly flaky systems that way. (add a taint bit, etc.,
>  > etc.)
>
>  It may even make sense to merge in the full memtest86. The code is small
>  (both source and binary) and IIRC it shares a lot of init code with x86.
>  The remaining problem would then be how to maintain its tests up do date.

memtester is another choice, and it is more easy to be merged.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/