All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bojan Prtvar <bojan.prtvar@rt-rk.com>
To: linux-mm@kvack.org
Subject: memtest help
Date: Thu, 28 Apr 2016 18:42:31 +0200	[thread overview]
Message-ID: <57223D77.6020502@rt-rk.com> (raw)

Hello everyone,

I need to test all RAM cells on a linux ARM embedded system. My use case 
is very similar to the one described in [1] expect the fact I also have 
strong requirements on minimizing the boot time impact.
Instead of doing that from the bootloader, I decided to evaluate the 
linux memtest feature introduced with [2].

My questions are:

1)
Does the  early_memtest() as called in [3] really covers *all* RAM cells?

2)
As memtest happens very early in boot stage, what primitives I can use 
to measure duration of early_memtest()? Are there any known heuristics? 
I need to test ~2GB of RAM.
This is my major concern.

3)
It seems reasonable to expose the number of detected bad cells to user 
space. I was thinking about sysfs. Are the patches welcomed?

[1]
http://www.linuxforums.org/forum/newbie/173847-how-do-memory-ram-test-when-linux-running.html
[2]
http://lkml.iu.edu/hypermail/linux/kernel/1503.1/00566.html
[3]
http://lxr.free-electrons.com/source/arch/arm/mm/init.c#L291

Thanks,
Bojan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2016-04-28 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 16:42 Bojan Prtvar [this message]
2016-04-29  9:22 ` memtest help Vladimir Murzin

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=57223D77.6020502@rt-rk.com \
    --to=bojan.prtvar@rt-rk.com \
    --cc=linux-mm@kvack.org \
    /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.