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: <20080321142919.GD31719@elte.hu>
Date:	Fri, 21 Mar 2008 15:29:19 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	yhlu.kernel@...il.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


* 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.)

	Ingo
--
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/