From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Yinghai Lu <yhlu.kernel.send@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86: memtest bootparam
Date: Mon, 21 Apr 2008 16:17:35 +0200 [thread overview]
Message-ID: <20080421141735.GS9554@elte.hu> (raw)
In-Reply-To: <86802c440804191354q45fdedelce0ec38ba52f3880@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > > OK. Did the new memtest feature get documented anywhere, btw?
> > > I'm only vaguely aware of its existence.
> >
> > Actually it would be nice if memtest was global, not x86-specific,
> > feature.
> >
> > I had some fun with arm running with 256mb, when only 128mb was
> > present. It booted succesfully...
>
> depends if you have find_e820_area_size in you platform. that need
> reserve_early...
>
> maybe we need to make reserve_early generic at first.
e820 is very x86 specific - i think the proper interface would be to
move the memtest feature to the bootmem subsystem. I.e. to run it once
all the early reservations have been flushed into bootmem - but before
we free all bootmem pages into the page allocator.
this still leaves a rather large amount of RAM to be tested, and keeps
it all cross-arch as well. Hm?
Ingo
next prev parent reply other threads:[~2008-04-21 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804181717.m3IHHicT031344@hera.kernel.org>
2008-04-18 21:52 ` x86: memtest bootparam Andrew Morton
2008-04-18 22:07 ` Yinghai Lu
2008-04-18 23:32 ` Andrew Morton
2008-04-19 0:03 ` Yinghai Lu
2008-04-19 13:33 ` Pavel Machek
2008-04-19 20:54 ` Yinghai Lu
2008-04-21 14:17 ` Ingo Molnar [this message]
2008-04-21 16:38 ` Yinghai Lu
[not found] <ak6MP-3wY-3@gated-at.bofh.it>
[not found] ` <ak6MP-3wY-1@gated-at.bofh.it>
2008-04-19 10:50 ` Bodo Eggert
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=20080421141735.GS9554@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=yhlu.kernel.send@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox