From: Ingo Molnar <mingo@elte.hu>
To: yhlu.kernel@gmail.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: early memtest to find bad ram
Date: Fri, 21 Mar 2008 13:03:13 +0100 [thread overview]
Message-ID: <20080321120313.GD25225@elte.hu> (raw)
In-Reply-To: <200803202358.33722.yhlu.kernel@gmail.com>
* Yinghai Lu <yhlu.kernel.send@gmail.com> wrote:
> do simple memtest after init_memory_mapping
>
> use find_e820_area_size to find all ram range that is not reserved.
>
> and do some simple bits test to find some bad ram.
>
> if find some bad ram, use reserve_early to exclude that range.
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.
a small style nit from scripts/checkpatch.pl:
> +// printk(KERN_DEBUG "find_e820_area_size : e820 %d [%llx, %lx]\n", i, ei->addr, ei_last);
remove such lines or make them pr_debug(). (checkpatch also found more
such cases)
also, please add a CONFIG_BOOTPARAM_MEMTEST=y option so that
distributions can enable this by default in their debug kernels.
i've applied your current version to get some testing, please send delta
patches against x86/latest.
Ingo
next prev parent reply other threads:[~2008-03-21 12:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 6:58 [PATCH] x86_64: early memtest to find bad ram Yinghai Lu
2008-03-21 12:03 ` Ingo Molnar [this message]
2008-03-21 13:08 ` H. Peter Anvin
2008-03-21 14:29 ` Ingo Molnar
2008-03-22 5:45 ` Willy Tarreau
2008-03-22 6:48 ` Yinghai Lu
2008-03-21 19:08 ` Yinghai Lu
2008-03-21 19:58 ` H. Peter Anvin
2008-03-21 20:09 ` Yinghai Lu
2008-03-21 21:22 ` Jan Engelhardt
2008-03-21 21:43 ` Yinghai Lu
2008-03-22 0:04 ` Yinghai Lu
2008-03-22 12:04 ` Ingo Molnar
2008-03-22 16:59 ` Yinghai Lu
2008-03-25 11:00 ` Ingo Molnar
2008-03-21 22:49 ` Sami Farin
2008-03-22 20:48 ` Arjan van de Ven
2008-03-22 21:01 ` H. Peter Anvin
2008-03-22 21:21 ` Yinghai Lu
2008-03-22 21:21 ` Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080321120313.GD25225@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.