public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: yhlu.kernel@gmail.com, yhlu.kernel.send@gmail.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: early memtest to find bad ram
Date: Sat, 22 Mar 2008 14:01:07 -0700	[thread overview]
Message-ID: <47E57393.7060606@zytor.com> (raw)
In-Reply-To: <20080322134814.7258ff0c@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Thu, 20 Mar 2008 23:58:33 -0700
> 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.
> 
> be careful, there's some special memory that e820 right now says is not reserved,
> but still has bios data (the first 4Kb of memory come to mind)
> 

Is that true even after Yinghai's changes?  I have lost track of all the 
patches...

	-hpa

  reply	other threads:[~2008-03-22 21:05 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
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 [this message]
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=47E57393.7060606@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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