All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	yhlu.kernel@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: early memtest to find bad ram
Date: Sat, 22 Mar 2008 06:45:37 +0100	[thread overview]
Message-ID: <20080322054537.GA23796@1wt.eu> (raw)
In-Reply-To: <20080321142919.GD31719@elte.hu>

On Fri, Mar 21, 2008 at 03:29:19PM +0100, Ingo Molnar wrote:
> 
> * H. Peter Anvin <hpa@zytor.com> wrote:
> 
> >> 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]
> >>
> >> one structural observation: please make this unified functionality, 
> >> so that 32-bit kernels can make use of it too.
> >>
> >
> > Indeed.  Of course, it would also be nice if distros shipped 
> > bootloader-invoked prekernel test software, like memtest86+, by 
> > default.
> 
> some do (Fedora for example), but it's still a bit quirky for users to 
> invoke and it would be nice to see those results in the kernel log as 
> well and flag possibly flaky systems that way. (add a taint bit, etc., 
> etc.)

It may even make sense to merge in the full memtest86. The code is small
(both source and binary) and IIRC it shares a lot of init code with x86.
The remaining problem would then be how to maintain its tests up do date.

Willy


  reply	other threads:[~2008-03-22  5:46 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 [this message]
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
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=20080322054537.GA23796@1wt.eu \
    --to=w@1wt.eu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.