linux-kernel - Re: [PATCH] x86_64: early memtest to find bad ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440803221421i544dc896qb63750237ffc50c4@mail.gmail.com>
Date:	Sat, 22 Mar 2008 14:21:45 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Arjan van de Ven" <arjan@...radead.org>,
	yhlu.kernel.send@...il.com,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86_64: early memtest to find bad ram

On Sat, Mar 22, 2008 at 2:01 PM, H. Peter Anvin <hpa@...or.com> wrote:
> Arjan van de Ven wrote:
>  > On Thu, 20 Mar 2008 23:58:33 -0700
>  > Yinghai Lu <yhlu.kernel.send@...il.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...

find_e820_area_size should be safe.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/