From: Andi Kleen <andi@firstfloor.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: make memtest support 32bit
Date: Tue, 15 Jul 2008 12:13:03 +0200 [thread overview]
Message-ID: <87lk03xxow.fsf@basil.nowhere.org> (raw)
In-Reply-To: <200807150003.44497.yhlu.kernel@gmail.com> (Yinghai Lu's message of "Tue, 15 Jul 2008 00:03:44 -0700")
Yinghai Lu <yhlu.kernel@gmail.com> writes:
> only support max_low_pfn below...
.... either add a fixmap or document that 32bit memtest will only
test a small fraction of the available memory on systems with >1GB.
In fact with this restriction it seems rather useless.
-Andi
next prev parent reply other threads:[~2008-07-15 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 7:02 [PATCH] x86: seperate memtest from init_64.c Yinghai Lu
2008-07-15 7:03 ` [PATCH] x86: make memtest support 32bit Yinghai Lu
2008-07-15 10:13 ` Andi Kleen [this message]
2008-07-18 12:12 ` Ingo Molnar
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=87lk03xxow.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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