Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758009AbYCUTIj (ORCPT ); Fri, 21 Mar 2008 15:08:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750844AbYCUTIb (ORCPT ); Fri, 21 Mar 2008 15:08:31 -0400 Received: from rv-out-0910.google.com ([209.85.198.184]:18135 "EHLO rv-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750702AbYCUTIa (ORCPT ); Fri, 21 Mar 2008 15:08:30 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WvFl7H3C4K0SJ7k7RqXVfZVvWtPL7cvkL122AkS8dbORfdksP/mB+MXlGKE3hua/fjNGoC95wY3HfuvRBO6B6Hm4rHqILLRpAoNcCcPoxrdc2QjCCQ/oI6r9GcZop1P9R+F6VMm7freyN5VahAY6tmMJhuHi+wJB80OzbZFdKfA= Message-ID: <86802c440803211208v40088eb1qe3f03977b220078@mail.gmail.com> Date: Fri, 21 Mar 2008 12:08:29 -0700 From: "Yinghai Lu" To: "H. Peter Anvin" Subject: Re: [PATCH] x86_64: early memtest to find bad ram Cc: "Ingo Molnar" , "Andrew Morton" , "kernel list" In-Reply-To: <47E3B335.3020501@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200803202358.33722.yhlu.kernel@gmail.com> <20080321120313.GD25225@elte.hu> <47E3B335.3020501@zytor.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1097 Lines: 27 On Fri, Mar 21, 2008 at 6:08 AM, H. Peter Anvin wrote: > Ingo Molnar 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. the current memtest86 is running in 32 bit mode, and only support 64G ram. I tried to expand that a bit, to support 1024g, but it only works on some machine. could be stack provide is not big enough? YH -- 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/