Date: Fri, 21 Mar 2008 15:29:19 +0100
From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: yhlu.kernel@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
       kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: early memtest to find bad ram
Message-ID: <20080321142919.GD31719@elte.hu>
References: <200803202358.33722.yhlu.kernel@gmail.com> <20080321120313.GD25225@elte.hu> <47E3B335.3020501@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47E3B335.3020501@zytor.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1055
Lines: 27


* H. Peter Anvin <hpa@zytor.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/