From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"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 14:43:08 -0700 [thread overview]
Message-ID: <86802c440803211443o7bbc539fx762e06f51c6f0fdb@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0803212221390.10642@fbirervta.pbzchgretzou.qr>
On Fri, Mar 21, 2008 at 2:22 PM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Mar 21 2008 13:03, Ingo Molnar wrote:
> > * 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]
>
> Perhaps this can even be used to provide on-the-fly badram
> patch semantics?
yes. but bad ranges can not be too many. otherwise early_res array
will overflow. then need to use memmap=nn$ss to exclude range already
found.
YH
next prev parent reply other threads:[~2008-03-21 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 6:58 Yinghai Lu
2008-03-21 12:03 ` Ingo Molnar
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 [this message]
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=86802c440803211443o7bbc539fx762e06f51c6f0fdb@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®